CreateBusinessContactPivotTable::up() - Code Metrics - Inspection of "Update laravel-auto-presenter dependency" - timegridio/concierge - Measure and Improve Code Quality continuously with Scrutinizer

Test Failed

Pull Request — master (#3)

unknown

created 2018-07-14 10:16 UTC

CreateBusinessContactPivotTable::up() A

↳ Parent: CreateBusinessContactPivotTable

Complexity

Conditions	1
Paths	1

Size

Total Lines

Duplication

Lines	0
Ratio	0 %

Code Coverage

Tests	10
CRAP Score	1

Importance

Changes

Metric	Value
dl	0
loc	13
ccs	10
cts	10
cp	1
rs	9.8333
c	0
b	0
f	0
cc	1
nc	1
nop	0
crap	1

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;

class CreateBusinessContactPivotTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('business_contact', function (Blueprint $table) {
            $table->integer('business_id')->unsigned()->index();
            $table->foreign('business_id')->references('id')->on('businesses')->onDelete('cascade');
            $table->integer('contact_id')->unsigned()->index();
            $table->foreign('contact_id')->references('id')->on('contacts')->onDelete('cascade');
            $table->string('notes')->nullable();
            $table->nullableTimestamps();

            $table->unique(['business_id', 'contact_id']);
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::drop('business_contact');
    }
}


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 2016-02-03 04:24 UTC by Report Bug Copy Issue Report 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

timegridio / concierge

Pull Request — master (#3)

CreateBusinessContactPivotTable::up() A

Complexity

Size

Duplication

Code Coverage

Importance

Duplication Side-by-Side

Filter issues like