AddDescriptionFieldForPermission::change() - Code Metrics - Inspection of "Merge pull request #8 from potievdev/feature/#7-ad..." - potievdev/slim-rbac - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( fe6d3f...aabe24 )

by ABDULMALIK

created 2017-12-24 16:15 UTC

AddDescriptionFieldForPermission::change() A

↳ Parent: AddDescriptionFieldForPermission

Complexity

Conditions	1
Paths	1

Size

Total Lines	8
Code Lines	5

Duplication

Lines	8
Ratio	100 %

Importance

Changes

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

<?php


use Phinx\Migration\AbstractMigration;

class AddDescriptionFieldForPermission extends AbstractMigration
namespace YourVendor;

class YourClass { }
{
    /**
     * Change Method.
     *
     * Write your reversible migrations using this method.
     *
     * More information on writing migrations is available here:
     * http://docs.phinx.org/en/latest/migrations.html#the-abstractmigration-class
     *
     * The following commands can be used in this method and Phinx will
     * automatically reverse them when rolling back:
     *
     *    createTable
     *    renameTable
     *    addColumn
     *    renameColumn
     *    addIndex
     *    addForeignKey
     *
     * Remember to call "create()" or "update()" and NOT "save()" when working
     * with the Table class.
     */
    public function change()
    {
        $permissionTable = $this->table('permission');

        $permissionTable
            ->addColumn('description', 'string', ['null' => true, 'comment' => 'description of permission'])
            ->update();
    }
}


1		<?php
2
3
4		use Phinx\Migration\AbstractMigration;
5
6	View Code Duplication	class AddDescriptionFieldForPermission extends AbstractMigration
		0 ignored issues – show Duplication introduced 2017-12-24 16:17 UTC by Report Bug Copy Issue Report This class 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... Coding Style Compatibility introduced 2017-12-24 16:17 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		* Change Method.
10		*
11		* Write your reversible migrations using this method.
12		*
13		* More information on writing migrations is available here:
14		* http://docs.phinx.org/en/latest/migrations.html#the-abstractmigration-class
15		*
16		* The following commands can be used in this method and Phinx will
17		* automatically reverse them when rolling back:
18		*
19		* createTable
20		* renameTable
21		* addColumn
22		* renameColumn
23		* addIndex
24		* addForeignKey
25		*
26		* Remember to call "create()" or "update()" and NOT "save()" when working
27		* with the Table class.
28		*/
29		public function change()
30		{
31		$permissionTable = $this->table('permission');
32
33		$permissionTable
34		->addColumn('description', 'string', ['null' => true, 'comment' => 'description of permission'])
35		->update();
36		}
37		}
38

potievdev / slim-rbac

Push — master ( fe6d3f...aabe24 )

AddDescriptionFieldForPermission::change() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like