CreateAttacherImagesTable::up() - Code Metrics - Inspection of "migration was namespaced! fixed" - CbCaio/Image-Attacher - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( 86e8e8...47d4e0 )

by Caio

created 2016-01-20 15:16 UTC

CreateAttacherImagesTable::up() A

↳ Parent: Project

Complexity

Conditions	1
Paths	1

Size

Total Lines	16
Code Lines	10

Duplication

Lines	0
Ratio	0 %

Importance

Changes	1
Bugs	0	Features	0

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

<?php
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
use Illuminate\Support\Facades\Schema;

class CreateAttacherImagesTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {

        Schema::create('attacher_images', function (Blueprint $table)

        {
            $table->increments('id');
            $table->unsignedInteger('owner_id')->index();
            $table->string('owner_type')->index();
            $table->string('file_extension');
            $table->string("file_name")->nullable();
            $table->smallInteger("file_size", FALSE, TRUE)->nullable();
            $table->string("mime_type")->nullable();
            $table->timestamps();
        });

    }

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


1			<?php
2			use Illuminate\Database\Schema\Blueprint;
3			use Illuminate\Database\Migrations\Migration;
4			use Illuminate\Support\Facades\Schema;
5
6			class CreateAttacherImagesTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2016-01-20 15:26 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
16			Schema::create('attacher_images', function (Blueprint $table)
			0 ignored issues – show Bug introduced 2016-01-20 12:45 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			{
18			$table->increments('id');
19			$table->unsignedInteger('owner_id')->index();
20			$table->string('owner_type')->index();
21			$table->string('file_extension');
22			$table->string("file_name")->nullable();
23			$table->smallInteger("file_size", FALSE, TRUE)->nullable();
24			$table->string("mime_type")->nullable();
25			$table->timestamps();
26			});
27
28			}
29
30			/**
31			* Reverse the migrations.
32			*
33			* @return void
34			*/
35			public function down()
36			{
37			Schema::drop('attacher_images');
38			}
39			}
40

CbCaio / Image-Attacher

Push — master ( 86e8e8...47d4e0 )

CreateAttacherImagesTable::up() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like