nicolaeturcan /
trainingresourceapp
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
| 1 | <?php |
||
| 2 | |||
| 3 | /* |
||
| 4 | |-------------------------------------------------------------------------- |
||
| 5 | | Application Routes |
||
| 6 | |-------------------------------------------------------------------------- |
||
| 7 | | |
||
| 8 | | Here is where you can register all of the routes for an application. |
||
| 9 | | It's a breeze. Simply tell Laravel the URIs it should respond to |
||
| 10 | | and give it the controller to call when that URI is requested. |
||
| 11 | | |
||
| 12 | */ |
||
| 13 | use App\Training_Resource; |
||
| 14 | |||
| 15 | Route::get('/', 'WelcomeController@index'); |
||
| 16 | |||
| 17 | |||
| 18 | Route::get('home', 'HomeController@index'); |
||
| 19 | |||
| 20 | /*Route::get('api/training_resource/parentid/{id}', function ($id) { |
||
|
0 ignored issues
–
show
|
|||
| 21 | return Training_Resource::where('training_resource_parentResourceId', '=', $id)->get(); |
||
| 22 | });*/ |
||
| 23 | |||
| 24 | Route::resource('api/training_resource', 'Training_Resource_Controller'); |
||
| 25 | |||
| 26 | Route::controllers([ |
||
| 27 | 'auth' => 'Auth\AuthController', |
||
| 28 | 'password' => 'Auth\PasswordController', |
||
| 29 | ]); |
||
| 30 |
Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.
The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.
This check looks for comments that seem to be mostly valid code and reports them.