CreateCustomersTable::up() - Code Metrics - Inspection of "Fixed menu make static issue" - Codexshaper/wpb-framework - Measure and Improve Code Quality continuously with Scrutinizer

Passed

Push — master ( 5cfb80...5d8a7b )

by CodexShaper

created 2020-06-29 17:32 UTC

CreateCustomersTable::up() A

↳ Parent: CreateCustomersTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	10
Code Lines	8

Duplication

Lines	0
Ratio	0 %

Importance

Changes

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

<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use CodexShaper\Database\Facades\Schema;
.
|-- OtherDir
|   |-- Bar.php
|   `-- Foo.php
`-- SomeDir
    `-- Foo.php

class CreateCustomersTable extends Migration
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('customers', function (Blueprint $table) {
            $table->id();
            $table->string('name');
            $table->string('email')->unique();
            $table->timestamp('email_verified_at')->nullable();
            $table->string('password');
            $table->rememberToken();
            $table->timestamps();
        });
    }

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


1			<?php
2
3			use Illuminate\Database\Migrations\Migration;
4			use Illuminate\Database\Schema\Blueprint;
5			use CodexShaper\Database\Facades\Schema;
			0 ignored issues – show Bug introduced 2020-06-29 17:11 UTC by Report Bug Copy Issue Report This use statement conflicts with another class in this namespace, `Schema`. Consider defining an alias. Let?s assume that you have a directory layout like this: . \|-- OtherDir \| \|-- Bar.php \| `-- Foo.php `-- SomeDir `-- Foo.php and let?s assume the following content of `Bar.php`: // Bar.php namespace OtherDir; use SomeDir\Foo; // This now conflicts the class OtherDir\Foo If both files `OtherDir/Foo.php` and `SomeDir/Foo.php` are loaded in the same runtime, you will see a PHP error such as the following: PHP Fatal error: Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php However, as `OtherDir/Foo.php` does not necessarily have to be loaded and the error is only triggered if it is loaded before `OtherDir/Bar.php`, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias: // Bar.php namespace OtherDir; use SomeDir\Foo as SomeDirFoo; // There is no conflict anymore. Loading history...
6
7			class CreateCustomersTable extends Migration
8			{
9			/**
10			* Run the migrations.
11			*
12			* @return void
13			*/
14			public function up()
15			{
16			Schema::create('customers', function (Blueprint $table) {
17			$table->id();
18			$table->string('name');
19			$table->string('email')->unique();
20			$table->timestamp('email_verified_at')->nullable();
21			$table->string('password');
22			$table->rememberToken();
23			$table->timestamps();
24			});
25			}
26
27			/**
28			* Reverse the migrations.
29			*
30			* @return void
31			*/
32			public function down()
33			{
34			Schema::dropIfExists('customers');
35			}
36			}
37

Codexshaper / wpb-framework

Push — master ( 5cfb80...5d8a7b )

CreateCustomersTable::up() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like