for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
class CreateNotificationsTable extends Migration
You can fix this by adding a namespace to your class:
namespace YourVendor; class YourClass { }
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.
{
/**
* Run the migrations.
* @return void
*/
public function up()
Schema::create('notification__notifications', function (Blueprint $table) {
$table->increments('id');
$table->integer('user_id')->unsigned();
$table->string('type')->nullable();
$table->string('icon_class');
$table->string('link')->nullable();
$table->string('title');
$table->string('message');
$table->boolean('is_read')->default(false);
$table->timestamps();
$table->foreign('user_id')->references('id')->on(config('auth.table', 'users'))->onDelete('cascade');
});
}
* Reverse the migrations.
public function down()
Schema::drop('notification__notifications');
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.