Total Complexity | 2 |
Total Lines | 29 |
Duplicated Lines | 0 % |
Changes | 1 | ||
Bugs | 0 | Features | 0 |
1 | <?php |
||
24 | class Create_Customers_Table extends Migration { |
||
25 | |||
26 | /** |
||
27 | * Run the migrations. |
||
28 | * |
||
29 | * @return void |
||
30 | */ |
||
31 | public function up() { |
||
32 | Schema::create( |
||
33 | 'customers', |
||
34 | function ( Blueprint $table ) { |
||
35 | $table->id(); |
||
36 | $table->string( 'name' ); |
||
37 | $table->string( 'email' )->unique(); |
||
38 | $table->timestamp( 'email_verified_at' )->nullable(); |
||
39 | $table->string( 'password' ); |
||
40 | $table->rememberToken(); |
||
41 | $table->timestamps(); |
||
42 | } |
||
43 | ); |
||
44 | } |
||
45 | |||
46 | /** |
||
47 | * Reverse the migrations. |
||
48 | * |
||
49 | * @return void |
||
50 | */ |
||
51 | public function down() { |
||
53 | } |
||
54 | } |
||
55 |
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: