ModifyUsersTable::up() - Code Metrics - afrittella/back-project - Measure and Improve Code Quality continuously with Scrutinizer

ModifyUsersTable::up() A
last analyzed 2018-02-11 23:44 UTC

↳ Parent: ModifyUsersTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	8
Code Lines	5

Duplication

Lines	8
Ratio	100 %

Importance

Changes

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

<?php

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

class ModifyUsersTable extends Migration
namespace YourVendor;

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

    {
        Schema::table('users', function(Blueprint $table) {
            $table->renameColumn('name', 'username');
            $table->boolean('confirmed')->default(0);
            $table->string('confirmation_code')->nullable();
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::table('users', function(Blueprint $table) {
        $table->renameColumn('username', 'name');
        $table->dropColumn('confirmed');
        $table->dropColumn('confirmation_code');
        });
    }
}


1		<?php
2
3		use Illuminate\Support\Facades\Schema;
4		use Illuminate\Database\Schema\Blueprint;
5		use Illuminate\Database\Migrations\Migration;
6
7		class ModifyUsersTable extends Migration
		0 ignored issues – show Coding Style Compatibility introduced 2017-04-07 07:13 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	View Code Duplication	public function up()
		0 ignored issues – show Duplication introduced 2017-10-18 05:42 UTC by Report Bug Copy Issue Report This method seems to be duplicated in your project. Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation. You can also find more detailed suggestions in the “Code” section of your repository. Loading history...
15		{
16		Schema::table('users', function(Blueprint $table) {
17		$table->renameColumn('name', 'username');
18		$table->boolean('confirmed')->default(0);
19		$table->string('confirmation_code')->nullable();
20		});
21		}
22
23		/**
24		* Reverse the migrations.
25		*
26		* @return void
27		*/
28		public function down()
29		{
30		Schema::table('users', function(Blueprint $table) {
31		$table->renameColumn('username', 'name');
32		$table->dropColumn('confirmed');
33		$table->dropColumn('confirmation_code');
34		});
35		}
36		}
37

afrittella / back-project

GitHub Access Token became invalid

ModifyUsersTable::up() A last analyzed 2018-02-11 23:44 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

ModifyUsersTable::up() A
last analyzed 2018-02-11 23:44 UTC