for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
<?php
use JetFire\Routing\RouteCollection;
require __DIR__.'/Autoload.php';
$autoload = new Autoload();
$autoload->addNamespace('JetFire\Routing',[
__DIR__.'/src/Routing',
__DIR__.'/',
]);
$autoload->addClass('Normal1Controller',__DIR__.'/Block1/Normal1Controller.php');
$autoload->register();
// Create RouteCollection instance
$collection = new RouteCollection();
$collection->addRoutes(__DIR__.'/Block1/routes.php',['view_dir'=>__DIR__.'/Block1/Views','prefix'=>'block']);
$router = new \JetFire\Routing\Router($collection);
$matcher = new \JetFire\Routing\Matcher\ArrayMatcher($router);
$router->addMatcher($matcher);
$matcher
object<JetFire\Routing\Matcher\ArrayMatcher>
string
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example:
function acceptsInteger($int) { } $x = '123'; // string "123" // Instead of acceptsInteger($x); // we recommend to use acceptsInteger((integer) $x);
$router->setResponses([
// you can use a closure to handle error
'404' => function(){
return '404';
},
'405' => function(){
return '405';
}
// Run it!
$router->run();
jetfirephp /
routing
Mugan27
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example: