1 | <?php |
||
2 | |||
3 | use Illuminate\Http\Request; |
||
0 ignored issues
–
show
|
|||
4 | use Illuminate\Support\Facades\Route; |
||
5 | |||
6 | /* |
||
7 | |-------------------------------------------------------------------------- |
||
8 | | Tool API Routes |
||
9 | |-------------------------------------------------------------------------- |
||
10 | | |
||
11 | | Here is where you may register API routes for your tool. These routes |
||
12 | | are loaded by the ServiceProvider of your tool. They are protected |
||
13 | | by your tool's "Authorize" middleware by default. Now, go build! |
||
14 | | |
||
15 | */ |
||
16 | |||
17 | // Route::get('/', function (Request $request) { |
||
18 | // // |
||
19 | // }); |
||
20 |
Let?s assume that you have a directory layout like this:
and let?s assume the following content of
Bar.php
:If both files
OtherDir/Foo.php
andSomeDir/Foo.php
are loaded in the same runtime, you will see a PHP error such as the following:PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php
However, as
OtherDir/Foo.php
does not necessarily have to be loaded and the error is only triggered if it is loaded beforeOtherDir/Bar.php
, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: