fadrian06
fadrian06
Here is another example of the requested behavior ```php Flight::route('/posts', PostController::class); ``` ```php class PostController { static function index(): void {} static function show(string $id): void {} } ``` Flight...
> Hi, > maybe i am late to the party, however would be better to use > > ```php > Flight::resource('/posts', PostController::class); > ``` > > Like Laravel and CI4...
Ok to start the tests for php 8 are excluded from the main suite, I run the tests of that specific class by hand
Calling the app directly instead of __callStatic does make sense because it would help the static analyzer
 
I have several ideas to solve it but I don't know how difficult it is to implement it and keep everything working as is. - Extract shared functionalities into traits...
I feel that the PR has covered something else related to the container, but I felt that I should fix it before dealing with other things.
Changes about the container ## Before If you install a psr11 compatible container, and pass it to `Flight::registerContainerHandler($container)`, works only if a class you have previously registered in the container....
please