Passed
Push — master ( 5a589d...727933 )
by Gabriel
03:07 queued 12s
created

AlterMailLogTableAddMessageIdColumn::up()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Importance

Changes 1
Bugs 0 Features 1
Metric Value
cc 1
eloc 2
c 1
b 0
f 1
nc 1
nop 0
dl 0
loc 4
rs 10
1
<?php
2
3
use Illuminate\Database\Migrations\Migration;
4
use Illuminate\Database\Schema\Blueprint;
5
use Illuminate\Support\Facades\Schema;
6
7
class AlterMailLogTableAddMessageIdColumn extends Migration
8
{
9
    /**
10
     * Run the migrations.
11
     *
12
     * @return void
13
     */
14
    public function up()
15
    {
16
        Schema::table('mail_log', function (Blueprint $table) {
17
            $table->string('message_id')->nullable()->unique();
18
        });
19
    }
20
21
    /**
22
     * Reverse the migrations.
23
     *
24
     * @return void
25
     */
26
    public function down()
27
    {
28
        Schema::table('mail_log', function (Blueprint $table) {
29
            $table->drop('message_id');
0 ignored issues
show
Unused Code introduced by
The call to Illuminate\Database\Schema\Blueprint::drop() has too many arguments starting with 'message_id'. ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-call  annotation

29
            $table->/** @scrutinizer ignore-call */ 
30
                    drop('message_id');

This check compares calls to functions or methods with their respective definitions. If the call has more arguments than are defined, it raises an issue.

If a function is defined several times with a different number of parameters, the check may pick up the wrong definition and report false positives. One codebase where this has been known to happen is Wordpress. Please note the @ignore annotation hint above.

Loading history...
30
        });
31
    }
32
}
33