Missing use statement should be avoided

More information: https://insight.symfony.com/what-we-analyse/php.missing_use_statement

Updated rule! We've recently tweaked this rule. This may explain the disappearance of false positives, or new suggestions not linked to any activity in the code.
  1. $password = $configExternal->get('laravel-salesforce::password');
  2. $token = $configExternal->get('laravel-salesforce::token');
  3. $this->sfh->login($username, $password . $token);
  4. } catch (Exception $e) {

    The Exception class resolves to the Davispeixoto\LaravelSalesforce\Exception class which PHP does not seem to be able to autoload.

    Time to fix: about 15 minutes
    Permalink
    Last edited by Davis L P Peixoto
  5. throw new SalesforceException('Exception at Constructor' . $e->getMessage() . "\n\n" . $e->getTraceAsString());
  6. }
  7. }
  8. public function __call($method, $args)