CreateFailedJobsTable::up() - Code Metrics - Inspection of "add queues container and move it's default config..." - Porto-SAP/Hello-API - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( f212e9...8e9014 )

by Mahmoud

created 2016-11-30 17:54 UTC

CreateFailedJobsTable::up() A

↳ Parent: CreateFailedJobsTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	11
Code Lines	8

Duplication

Lines	0
Ratio	0 %

Importance

Changes

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

<?php

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

class CreateFailedJobsTable extends Migration
namespace YourVendor;

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

            $table->increments('id');
            $table->text('connection');
            $table->text('queue');
            $table->longText('payload');
            $table->longText('exception');
            $table->timestamp('failed_at')->useCurrent();
        });
    }

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


1			<?php
2
3			use Illuminate\Support\Facades\Schema;
4			use Illuminate\Database\Schema\Blueprint;
5			use Illuminate\Database\Migrations\Migration;
6
7			class CreateFailedJobsTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2016-11-30 17:58 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('failed_jobs', function (Blueprint $table) {
			0 ignored issues – show Bug introduced 2016-11-30 17:58 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...
17			$table->increments('id');
18			$table->text('connection');
19			$table->text('queue');
20			$table->longText('payload');
21			$table->longText('exception');
22			$table->timestamp('failed_at')->useCurrent();
23			});
24			}
25
26			/**
27			* Reverse the migrations.
28			*
29			* @return void
30			*/
31			public function down()
32			{
33			Schema::dropIfExists('failed_jobs');
34			}
35			}
36

Porto-SAP / Hello-API

Push — master ( f212e9...8e9014 )

CreateFailedJobsTable::up() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like