CreateChangesTable::up() - Code Metrics - cviebrock/eloquent-loggable - Measure and Improve Code Quality continuously with Scrutinizer

CreateChangesTable::up() A
last analyzed 2017-07-06 14:14 UTC

↳ Parent: CreateChangesTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	20
Code Lines	16

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
dl	0
loc	20
rs	9.4285
c	0
b	0
f	0
cc	1
eloc	16
nc	1
nop	0

<?php

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


class CreateChangesTable extends Migration
namespace YourVendor;

class YourClass { }
{

    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('loggable_changes', function(Blueprint $table) {

            $table->increments('id');
            $table->unsignedInteger('user_id');
            $table->unsignedInteger('model_id');
            $table->string('model_type');
            $table->enum('type', ['create', 'update', 'delete', 'restore'])->default('update');
            $table->string('set', 32)->nullable();
            $table->string('attribute')->nullable();
            $table->text('old_value')->nullable();
            $table->text('new_value')->nullable();
            $table->timestamps();

            $table->index('user_id');
            $table->index('model_id');
            $table->index('type');
            $table->index('set');
        });
    }

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

}


1			<?php
2
3			use Illuminate\Database\Migrations\Migration;
4			use Illuminate\Database\Schema\Blueprint;
5			use Illuminate\Support\Facades\Schema;
6
7
8			class CreateChangesTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2017-07-06 14:12 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...
9			{
10
11			/**
12			* Run the migrations.
13			*
14			* @return void
15			*/
16			public function up()
17			{
18			Schema::create('loggable_changes', function(Blueprint $table) {
			0 ignored issues – show Bug introduced 2017-07-06 14:12 UTC by Report Bug Copy Issue Report The method `create()` does not exist on `Illuminate\Support\Facades\Schema`. Did you maybe mean `createFreshMockInstance()`? This check marks calls to methods that do not seem to exist on an object. This is most likely the result of a method being renamed without all references to it being renamed likewise. Loading history...
19			$table->increments('id');
20			$table->unsignedInteger('user_id');
21			$table->unsignedInteger('model_id');
22			$table->string('model_type');
23			$table->enum('type', ['create', 'update', 'delete', 'restore'])->default('update');
24			$table->string('set', 32)->nullable();
25			$table->string('attribute')->nullable();
26			$table->text('old_value')->nullable();
27			$table->text('new_value')->nullable();
28			$table->timestamps();
29
30			$table->index('user_id');
31			$table->index('model_id');
32			$table->index('type');
33			$table->index('set');
34			});
35			}
36
37			/**
38			* Reverse the migrations.
39			*
40			* @return void
41			*/
42			public function down()
43			{
44			Schema::dropTable('loggable_changes');
45			}
46
47			}
48

cviebrock / eloquent-loggable

CreateChangesTable::up() A last analyzed 2017-07-06 14:14 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

CreateChangesTable::up() A
last analyzed 2017-07-06 14:14 UTC