CreateEnrollmentsTable::up() - Code Metrics - Inspection of "Enrollment table to enrollments and changed provid..." - manelgavalda/enrollment_mobile - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( d9cb28...e29950 )

by Manel

created 2016-12-17 17:17 UTC

CreateEnrollmentsTable::up() A

↳ Parent: CreateEnrollmentsTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	14
Code Lines	9

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
dl	0
loc	14
rs	9.4285
c	0
b	0
f	0
cc	1
eloc	9
nc	1
nop	0

<?php

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

class CreateEnrollmentsTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create('enrollments', function (Blueprint $table) {

            $table->increments('id'); //obligatori
            $table->boolean('validated'); //només les vàlides són actives.
            $table->boolean('finished'); //indica si la matricula està finalitzada.
            //$table->integer('period_id'); //De moment descartat //obligatori

            $table->integer('study_id');
            $table->integer('course_id');
            $table->integer('classroom_id');
            $table->timestamps(); //timestamps
            //$table->userstamps();

        });
    }

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


1			<?php
2
3			use Illuminate\Support\Facades\Schema;
4			use Illuminate\Database\Schema\Blueprint;
5			use Illuminate\Database\Migrations\Migration;
6
7			class CreateEnrollmentsTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2016-12-17 17:20 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			public function up()
15			{
16			Schema::create('enrollments', function (Blueprint $table) {
			0 ignored issues – show Bug introduced 2016-12-17 17:20 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			$table->increments('id'); //obligatori
18			$table->boolean('validated'); //només les vàlides són actives.
19			$table->boolean('finished'); //indica si la matricula està finalitzada.
20			//$table->integer('period_id'); //De moment descartat //obligatori
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-12-01 11:38 UTC by Report Bug Copy Issue Report `75%` 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->integer('study_id');
22			$table->integer('course_id');
23			$table->integer('classroom_id');
24			$table->timestamps(); //timestamps
25			//$table->userstamps();
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-12-01 11:38 UTC by Report Bug Copy Issue Report `84%` 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...
26			});
27			}
28
29			/**
30			* Reverse the migrations.
31			*
32			* @return void
33			*/
34			public function down()
35			{
36			Schema::dropIfExists('enrollment');
37			}
38			}
39

manelgavalda / enrollment_mobile

Push — master ( d9cb28...e29950 )

CreateEnrollmentsTable::up() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like