jon48/webtrees-lib

View on GitHub
app/Module/Sosa/Http/RequestHandlers/MissingAncestorsList.php

Summary

Maintainability
A
2 hrs
Test Coverage

Method handle has 44 lines of code (exceeds 25 allowed). Consider refactoring.
Open

    public function handle(ServerRequestInterface $request): ResponseInterface
    {
        if ($this->module === null) {
            throw new HttpNotFoundException(I18N::translate('The attached module could not be found.'));
        }
Severity: Minor
Found in app/Module/Sosa/Http/RequestHandlers/MissingAncestorsList.php - About 1 hr to fix

    Avoid too many return statements within this method.
    Open

            return $this->viewResponse($this->module->name() . '::list-missing-page', [
                'module_name'       =>  $this->module->name(),
                'title'             =>  I18N::translate('Missing Ancestors'),
                'tree'              =>  $tree,
                'root_indi'         =>  $sosa_stats_service->rootIndividual(),
    Severity: Major
    Found in app/Module/Sosa/Http/RequestHandlers/MissingAncestorsList.php - About 30 mins to fix

      The class MissingAncestorsList has a coupling between objects value of 14. Consider to reduce the number of dependencies under 13.
      Open

      class MissingAncestorsList implements RequestHandlerInterface
      {
          use ViewResponseTrait;
      
          /**

      CouplingBetweenObjects

      Since: 1.1.0

      A class with too many dependencies has negative impacts on several quality aspects of a class. This includes quality criteria like stability, maintainability and understandability

      Example

      class Foo {
          /**
           * @var \foo\bar\X
           */
          private $x = null;
      
          /**
           * @var \foo\bar\Y
           */
          private $y = null;
      
          /**
           * @var \foo\bar\Z
           */
          private $z = null;
      
          public function setFoo(\Foo $foo) {}
          public function setBar(\Bar $bar) {}
          public function setBaz(\Baz $baz) {}
      
          /**
           * @return \SplObjectStorage
           * @throws \OutOfRangeException
           * @throws \InvalidArgumentException
           * @throws \ErrorException
           */
          public function process(\Iterator $it) {}
      
          // ...
      }

      Source https://phpmd.org/rules/design.html#couplingbetweenobjects

      Avoid using static access to class '\Fisharebest\Webtrees\Auth' in method 'handle'.
      Open

              $user = Auth::check() ? Validator::attributes($request)->user() : new DefaultUser();

      StaticAccess

      Since: 1.4.0

      Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

      Example

      class Foo
      {
          public function bar()
          {
              Bar::baz();
          }
      }

      Source https://phpmd.org/rules/cleancode.html#staticaccess

      Avoid using static access to class '\Fisharebest\Webtrees\I18N' in method 'handle'.
      Open

                  'title'             =>  I18N::translate('Missing Ancestors'),

      StaticAccess

      Since: 1.4.0

      Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

      Example

      class Foo
      {
          public function bar()
          {
              Bar::baz();
          }
      }

      Source https://phpmd.org/rules/cleancode.html#staticaccess

      Avoid using static access to class '\Fisharebest\Webtrees\I18N' in method 'handle'.
      Open

                  throw new HttpNotFoundException(I18N::translate('The attached module could not be found.'));

      StaticAccess

      Since: 1.4.0

      Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

      Example

      class Foo
      {
          public function bar()
          {
              Bar::baz();
          }
      }

      Source https://phpmd.org/rules/cleancode.html#staticaccess

      There are no issues that match your filters.

      Category
      Status