CreateUsersTable   A
last analyzed

Complexity

Total Complexity 2

Size/Duplication

Total Lines 36
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 2

Test Coverage

Coverage 80%

Importance

Changes 0
Metric Value
wmc 2
lcom 0
cbo 2
dl 0
loc 36
ccs 12
cts 15
cp 0.8
rs 10
c 0
b 0
f 0

2 Methods

Rating   Name   Duplication   Size   Complexity  
A up() 0 17 1
A down() 0 4 1
1
<?php
2
3
use Illuminate\Database\Schema\Blueprint;
4
use Illuminate\Database\Migrations\Migration;
5
6
class CreateUsersTable 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 9
		Schema::create('users', function(Blueprint $table)
16
		{
17 9
			$table->increments('id');
18 9
			$table->string('username', 16);
19 9
			$table->string('displayname', 128)->nullable();
20 9
			$table->string('email')->nullable();
21 9
			$table->boolean('admin')->default(false);
22
23 9
			$table->rememberToken();
24 9
			$table->timestamps();
25
26 9
			$table->unique('username');
27 9
			$table->unique('email');
28 9
		});
29 9
	}
30
31
	/**
32
	 * Reverse the migrations.
33
	 *
34
	 * @return void
35
	 */
36
	public function down()
37
	{
38
		Schema::drop('users');
39
	}
40
41
}
42