CreateNotificationsTable::up() - Code Metrics - Inspection of "Apply fixes from StyleCI (#168)" - webshelf/framework - Measure and Improve Code Quality continuously with Scrutinizer

Passed

Branch — master (114f68)

by Mark

created 2018-05-14 00:45 UTC

CreateNotificationsTable::up() A

↳ Parent: CreateNotificationsTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	10
Code Lines	8

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	1
eloc	8
nc	1
nop	0
dl	0
loc	10
rs	9.4285
c	0
b	0
f	0

<?php

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

class CreateNotificationsTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        \Schema::create('notifications', function (Blueprint $table) {
            $table->increments('id');
            $table->unsignedInteger('account_id')->nullable();
            $table->integer('level')->nullable();
            $table->string('message');
            $table->timestamp('read_at')->nullable();
            $table->softDeletes();
            $table->timestamps();
        });
    }

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


1			<?php
2
3			use Illuminate\Database\Schema\Blueprint;
4			use Illuminate\Database\Migrations\Migration;
5
6			class CreateNotificationsTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2018-05-14 00:54 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			\Schema::create('notifications', function (Blueprint $table) {
16			$table->increments('id');
17			$table->unsignedInteger('account_id')->nullable();
18			$table->integer('level')->nullable();
19			$table->string('message');
20			$table->timestamp('read_at')->nullable();
21			$table->softDeletes();
22			$table->timestamps();
23			});
24			}
25
26			/**
27			* Reverse the migrations.
28			*
29			* @return void
30			*/
31			public function down()
32			{
33			\Schema::dropIfExists('notifications');
34			}
35			}
36

webshelf / framework

Scrutinizer GitHub App not installed

Branch — master (114f68)

CreateNotificationsTable::up() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like