CreateNotificationLogsTable::down() - Code Metrics - webelightdev/laravel-push-notification - Measure and Improve Code Quality continuously with Scrutinizer

CreateNotificationLogsTable::down() A
last analyzed 2017-06-21 05:24 UTC

↳ Parent: CreateNotificationLogsTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	4
Code Lines	2

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
dl	0
loc	4
rs	10
c	0
b	0
f	0
cc	1
eloc	2
nc	1
nop	0

<?php

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

class CreateNotificationLogsTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('notification_logs', function (Blueprint $table) {
            $table->increments('id');
            $table->timestamps();
            $table->longtext('device_token')->nullable();
            $table->longtext('notification_message')->nullable();
            $table->longtext('error_message')->nullable();
            $table->enum('status', ['success', 'failure']);
        });
    }

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


1			<?php
2
3			use Illuminate\Database\Migrations\Migration;
4			use Illuminate\Database\Schema\Blueprint;
5			use Illuminate\Support\Facades\Schema;
6
7			class CreateNotificationLogsTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2017-05-26 12:29 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('notification_logs', function (Blueprint $table) {
17			$table->increments('id');
18			$table->timestamps();
19			$table->longtext('device_token')->nullable();
20			$table->longtext('notification_message')->nullable();
21			$table->longtext('error_message')->nullable();
22			$table->enum('status', ['success', 'failure']);
23			});
24			}
25
26			/**
27			* Reverse the migrations.
28			*
29			* @return void
30			*/
31			public function down()
32			{
33			Schema::dropIfExists('notification_logs');
34			}
35			}
36

webelightdev / laravel-push-notification

GitHub Access Token became invalid

CreateNotificationLogsTable::down() A last analyzed 2017-06-21 05:24 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

CreateNotificationLogsTable::down() A
last analyzed 2017-06-21 05:24 UTC