CreateAliveMessageEventsTable::up() - Code Metrics - Alive2212/LaravelMessageService - Measure and Improve Code Quality continuously with Scrutinizer

CreateAliveMessageEventsTable::up() A
last analyzed 2018-06-19 12:24 UTC

↳ Parent: CreateAliveMessageEventsTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	19
Code Lines	11

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
dl	0
loc	19
rs	9.4285
c	0
b	0
f	0
cc	1
eloc	11
nc	1
nop	0

<?php

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

class CreateAliveMessageEventsTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('alive_message_events', function (Blueprint $table) {
            $table->increments('id');

            $table->text('model');

            $table->enum('type', [
                'Saving', 'Creating', 'Updating', 'Deleting', 'Restoring',
                'Saved', 'Created', 'Updated', 'Deleted', 'Restored',
                'pivotAttaching', 'pivotDetaching', 'pivotUpdating',
                'pivotAttached', 'pivotDetached', 'pivotUpdated',
            ]);

            $table->text('rules');

            $table->timestamps();
        });
    }

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


1			<?php
2
3			use Illuminate\Support\Facades\Schema;
4			use Illuminate\Database\Schema\Blueprint;
5			use Illuminate\Database\Migrations\Migration;
6
7			class CreateAliveMessageEventsTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2018-04-30 14:33 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...
8			{
9			/**
10			* Run the migrations.
11			*
12			* @return void
13			*/
14			public function up()
15			{
16			Schema::create('alive_message_events', function (Blueprint $table) {
17			$table->increments('id');
18
19			$table->text('model');
20
21			$table->enum('type', [
22			'Saving', 'Creating', 'Updating', 'Deleting', 'Restoring',
23			'Saved', 'Created', 'Updated', 'Deleted', 'Restored',
24			'pivotAttaching', 'pivotDetaching', 'pivotUpdating',
25			'pivotAttached', 'pivotDetached', 'pivotUpdated',
26			]);
27
28			$table->text('rules');
29
30			$table->timestamps();
31			});
32			}
33
34			/**
35			* Reverse the migrations.
36			*
37			* @return void
38			*/
39			public function down()
40			{
41			Schema::dropIfExists('alive_message_events');
42			}
43			}
44

Alive2212 / LaravelMessageService

CreateAliveMessageEventsTable::up() A last analyzed 2018-06-19 12:24 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

CreateAliveMessageEventsTable::up() A
last analyzed 2018-06-19 12:24 UTC