CreateHistoriesTable   A
last analyzed

Complexity

Total Complexity 2

Size/Duplication

Total Lines 35
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 1

Importance

Changes 0
Metric Value
dl 0
loc 35
rs 10
c 0
b 0
f 0
wmc 2
lcom 0
cbo 1

2 Methods

Rating   Name   Duplication   Size   Complexity  
A up() 0 17 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 CreateHistoriesTable 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('histories', function (Blueprint $table) {
17
            $table->increments('id');
18
            $table->uuid('uuid')->unique();
19
            $table->string('content_type');
20
            $table->integer('content_id');
21
            $table->integer('workflow_id')->unsigned()->nullable();           
22
            $table->integer('workflow_transition_id')->unsigned()->nullable();            
23
            $table->integer('from_state');
24
            $table->integer('to_state');
25
            $table->integer('user_id');
26
            $table->text('message');
27
            $table->softDeletes();
28
            $table->timestamps();
29
        });
30
    }
31
32
    /**
33
     * Reverse the migrations.
34
     *
35
     * @return void
36
     */
37
    public function down()
38
    {        
39
        Schema::dropIfExists('histories'); 
40
    }
41
}
42