CreateNotificationsTable::down()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
dl 0
loc 4
rs 10
c 0
b 0
f 0
cc 1
eloc 2
nc 1
nop 0
1
<?php
2
3
use Illuminate\Database\Migrations\Migration;
4
use Illuminate\Database\Schema\Blueprint;
5
6
class CreateNotificationsTable extends Migration
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

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.

Loading history...
7
{
8
    /**
9
     * Run the migrations.
10
     * @return void
11
     */
12
    public function up()
13
    {
14
        Schema::create('notification__notifications', function (Blueprint $table) {
15
            $table->increments('id');
16
            $table->integer('user_id')->unsigned();
17
            $table->string('type')->nullable();
18
            $table->string('icon_class');
19
            $table->string('link')->nullable();
20
            $table->string('title');
21
            $table->string('message');
22
            $table->boolean('is_read')->default(false);
23
            $table->timestamps();
24
            $table->foreign('user_id')->references('id')->on(config('auth.table', 'users'))->onDelete('cascade');
25
        });
26
    }
27
28
    /**
29
     * Reverse the migrations.
30
     * @return void
31
     */
32
    public function down()
33
    {
34
        Schema::drop('notification__notifications');
35
    }
36
}
37