CreatePelayananKesehatanTable::up() - Code Metrics - Inspection of "reinit project" - bantenprov/retribusi-pelayanan-kesehatan - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( 1c55d7...55a2f4 )

unknown

created 2018-05-12 06:48 UTC

CreatePelayananKesehatanTable::up() A

↳ Parent: CreatePelayananKesehatanTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	17
Code Lines	13

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	1
eloc	13
nc	1
nop	0
dl	0
loc	17
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;
use Kalnoy\Nestedset\NestedSet;



class CreatePelayananKesehatanTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('pelanan_kesehatan', function (Blueprint $table) {
            //$table->increments('id');

            $table->uuid('id')->unique();
            $table->primary('id');
            $table->string('kunker')->index();
            $table->string('name');
            $table->string('kunker_sinjab')->nullable();            
            $table->string('kunker_simral')->nullable();
            $table->integer('levelunker');
            $table->string('njab');
            $table->string('npej');
            NestedSet::columns($table);
            $table->timestamps();   
        });
    }

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


1			<?php
2
3			use Illuminate\Support\Facades\Schema;
4			use Illuminate\Database\Schema\Blueprint;
5			use Illuminate\Database\Migrations\Migration;
6			use Kalnoy\Nestedset\NestedSet;
7
8
9
10			class CreatePelayananKesehatanTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2018-05-11 12:48 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...
11			{
12			/**
13			* Run the migrations.
14			*
15			* @return void
16			*/
17			public function up()
18			{
19			Schema::create('pelanan_kesehatan', function (Blueprint $table) {
20			//$table->increments('id');
			0 ignored issues – show Unused Code Comprehensibility introduced 2018-05-11 12:48 UTC by Report Bug Copy Issue Report `86%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
21			$table->uuid('id')->unique();
22			$table->primary('id');
23			$table->string('kunker')->index();
24			$table->string('name');
25			$table->string('kunker_sinjab')->nullable();
26			$table->string('kunker_simral')->nullable();
27			$table->integer('levelunker');
28			$table->string('njab');
29			$table->string('npej');
30			NestedSet::columns($table);
31			$table->timestamps();
32			});
33			}
34
35			/**
36			* Reverse the migrations.
37			*
38			* @return void
39			*/
40			public function down()
41			{
42			Schema::dropIfExists('pelanan_kesehatan');
43			}
44			}
45

bantenprov / retribusi-pelayanan-kesehatan

Push — master ( 1c55d7...55a2f4 )

CreatePelayananKesehatanTable::up() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like