CreateBusinessContactPivotTable   A
last analyzed

Complexity

Total Complexity 2

Size/Duplication

Total Lines 31
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 2

Test Coverage

Coverage 76.92%

Importance

Changes 0
Metric Value
wmc 2
lcom 0
cbo 2
dl 0
loc 31
ccs 10
cts 13
cp 0.7692
rs 10
c 0
b 0
f 0

2 Methods

Rating   Name   Duplication   Size   Complexity  
A up() 0 13 1
A down() 0 4 1
1
<?php
2
3
use Illuminate\Database\Migrations\Migration;
4
use Illuminate\Database\Schema\Blueprint;
5
6
class CreateBusinessContactPivotTable 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
     *
11
     * @return void
12
     */
13
    public function up()
14
    {
15 152
        Schema::create('business_contact', function (Blueprint $table) {
16 152
            $table->integer('business_id')->unsigned()->index();
17 152
            $table->foreign('business_id')->references('id')->on('businesses')->onDelete('cascade');
18 152
            $table->integer('contact_id')->unsigned()->index();
19 152
            $table->foreign('contact_id')->references('id')->on('contacts')->onDelete('cascade');
20 152
            $table->string('notes')->nullable();
21 152
            $table->nullableTimestamps();
22
23 152
            $table->unique(['business_id', 'contact_id']);
24 152
        });
25 152
    }
26
27
    /**
28
     * Reverse the migrations.
29
     *
30
     * @return void
31
     */
32
    public function down()
33
    {
34
        Schema::drop('business_contact');
35
    }
36
}
37