These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
2 | |||
3 | use Illuminate\Support\Facades\Schema; |
||
4 | use Illuminate\Database\Schema\Blueprint; |
||
5 | use Illuminate\Database\Migrations\Migration; |
||
6 | |||
7 | class AddUserNameToUsersTable extends Migration |
||
0 ignored issues
–
show
|
|||
8 | { |
||
9 | /** |
||
10 | * Run the migrations. |
||
11 | * |
||
12 | * @return void |
||
13 | */ |
||
14 | public function up() |
||
15 | { |
||
16 | Schema::table('users', function (Blueprint $table) { |
||
17 | $table->string('username')->unique()->nullable()->after('name'); |
||
18 | }); |
||
19 | } |
||
20 | |||
21 | /** |
||
22 | * Reverse the migrations. |
||
23 | * |
||
24 | * @return void |
||
25 | */ |
||
26 | public function down() |
||
27 | { |
||
28 | Schema::table('users', function (Blueprint $table) { |
||
29 | $table->dropColumn('username'); |
||
30 | }); |
||
31 | } |
||
32 | } |
||
33 |
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.