xervice /
service
| 1 | <?php |
||||||
| 2 | |||||||
| 3 | error_reporting(E_ALL); |
||||||
| 4 | ini_set('display_errors', 1); |
||||||
| 5 | |||||||
| 6 | use Xervice\Core\Locator\Locator; |
||||||
| 7 | |||||||
| 8 | require __DIR__ . '/../vendor/autoload.php'; |
||||||
| 9 | |||||||
| 10 | putenv("APPLICATION_PATH=".dirname(__DIR__)); |
||||||
| 11 | |||||||
| 12 | $locator = Locator::getInstance(); |
||||||
| 13 | $locator->service()->facade()->registerHandler(); |
||||||
|
0 ignored issues
–
show
The method
registerHandler() does not exist on Xervice\Core\Facade\FacadeInterface. It seems like you code against a sub-type of Xervice\Core\Facade\FacadeInterface such as Xervice\Service\ServiceFacade.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
|
|||||||
| 14 | $locator->service()->facade()->startApplication(); |
||||||
|
0 ignored issues
–
show
The method
startApplication() does not exist on Xervice\Core\Facade\FacadeInterface. It seems like you code against a sub-type of Xervice\Core\Facade\FacadeInterface such as Xervice\Service\ServiceFacade.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
Loading history...
The method
startApplication() does not exist on Xervice\Core\Facade\EmptyFacade.
(
Ignorable by Annotation
)
If this is a false-positive, you can also ignore this issue in your code via the
This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
|
|||||||
| 15 |
This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces.
This is most likely a typographical error or the method has been renamed.