CreateAliveMessageEventsTable   A
last analyzed

Complexity

Total Complexity 2

Size/Duplication

Total Lines 37
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 3

Importance

Changes 0
Metric Value
wmc 2
lcom 0
cbo 3
dl 0
loc 37
rs 10
c 0
b 0
f 0

2 Methods

Rating   Name   Duplication   Size   Complexity  
A up() 0 19 1
A down() 0 4 1
1
<?php
2
3
use Illuminate\Support\Facades\Schema;
4
use Illuminate\Database\Schema\Blueprint;
5
use Illuminate\Database\Migrations\Migration;
6
7
class CreateAliveMessageEventsTable 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...
8
{
9
    /**
10
     * Run the migrations.
11
     *
12
     * @return void
13
     */
14
    public function up()
15
    {
16
        Schema::create('alive_message_events', function (Blueprint $table) {
17
            $table->increments('id');
18
19
            $table->text('model');
20
21
            $table->enum('type', [
22
                'Saving', 'Creating', 'Updating', 'Deleting', 'Restoring',
23
                'Saved', 'Created', 'Updated', 'Deleted', 'Restored',
24
                'pivotAttaching', 'pivotDetaching', 'pivotUpdating',
25
                'pivotAttached', 'pivotDetached', 'pivotUpdated',
26
            ]);
27
28
            $table->text('rules');
29
30
            $table->timestamps();
31
        });
32
    }
33
34
    /**
35
     * Reverse the migrations.
36
     *
37
     * @return void
38
     */
39
    public function down()
40
    {
41
        Schema::dropIfExists('alive_message_events');
42
    }
43
}
44