AddReason::up()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 7

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
dl 0
loc 7
rs 10
c 0
b 0
f 0
cc 1
nc 1
nop 0
1
<?php
2
3
use Illuminate\Database\Schema\Blueprint;
4
use Illuminate\Database\Migrations\Migration;
5
6
class AddReason extends Migration {
0 ignored issues
show
Coding Style Compatibility introduced by
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
	 * Run the migrations.
10
	 *
11
	 * @return void
12
	 */
13
	public function up()
14
	{
15
		Schema::table('versions', function(Blueprint $table)
16
		{
17
            $table->string('reason', 100)->nullable()->after('model_data');
18
		});
19
	}
20
21
	/**
22
	 * Reverse the migrations.
23
	 *
24
	 * @return void
25
	 */
26
	public function down()
27
	{
28
		Schema::table('versions', function(Blueprint $table)
29
		{
30
            $table->dropColumn('reason');
31
		});
32
	}
33
34
}
35