CreateTeamUsersTable   A
last analyzed

Complexity

Total Complexity 2

Size/Duplication

Total Lines 37
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 2

Test Coverage

Coverage 81.25%

Importance

Changes 0
Metric Value
wmc 2
lcom 0
cbo 2
dl 0
loc 37
ccs 13
cts 16
cp 0.8125
rs 10
c 0
b 0
f 0

2 Methods

Rating   Name   Duplication   Size   Complexity  
A up() 0 18 1
A down() 0 4 1
1
<?php
2
3
use Illuminate\Database\Schema\Blueprint;
4
use Illuminate\Database\Migrations\Migration;
5
6
class CreateTeamUsersTable 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('league_team_user', function(Blueprint $table)
16
		{
17 9
			$table->increments('id');
18 9
			$table->unsignedInteger('league_team_id');
19 9
			$table->unsignedInteger('user_id');
20 9
			$table->timestamps();
21
22 9
			$table->foreign('league_team_id')
23 9
				->references('id')->on('league_teams')
24 9
				->onDelete('cascade')->onUpdate('cascade');
25
26 9
			$table->foreign('user_id')
27 9
				->references('id')->on('users')
28 9
				->onDelete('cascade')->onUpdate('cascade');
29 9
		});
30 9
	}
31
32
	/**
33
	 * Reverse the migrations.
34
	 *
35
	 * @return void
36
	 */
37
	public function down()
38
	{
39
		Schema::drop('league_team_user');
40
	}
41
42
}
43