CreateMailmanMessagesTable::up() - Code Metrics - qodeboy/laravel-mailman - Measure and Improve Code Quality continuously with Scrutinizer

CreateMailmanMessagesTable::up() B
last analyzed 2017-10-03 14:51 UTC

↳ Parent: CreateMailmanMessagesTable

Complexity

Conditions	1
Paths	1

Size

Total Lines	25
Code Lines	15

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
dl	0
loc	25
rs	8.8571
c	0
b	0
f	0
cc	1
eloc	15
nc	1
nop	0

<?php

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

class CreateMailmanMessagesTable extends Migration
namespace YourVendor;

class YourClass { }
{
    /**
     * Run the migrations.
     *
     * @return void
     */
    public function up()
    {
        Schema::create(config('mailman.storage.database.table'), function (Blueprint $table) {
            $table->increments('id')->unsigned();

            $table->string('message_id', 512);
            $table->string('content_type', 64);

            $table->enum('status', ['allowed', 'denied']);

            $table->mediumText('from', 512);

            $table->mediumText('to', 512);

            $table->mediumText('reply_to', 512)->nullable();


            $table->mediumText('cc')->nullable();
            $table->mediumText('bcc')->nullable();

            $table->string('subject');
            $table->mediumText('body');

            $table->mediumText('instance');

            $table->timestamps();
        });
    }

    /**
     * Reverse the migrations.
     *
     * @return void
     */
    public function down()
    {
        Schema::drop(config('mailman.storage.database.table'));
    }
}


1			<?php
2
3			use Illuminate\Database\Migrations\Migration;
4			use Illuminate\Database\Schema\Blueprint;
5
6			class CreateMailmanMessagesTable extends Migration
			0 ignored issues – show Coding Style Compatibility introduced 2016-04-12 16:51 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...
7			{
8			/**
9			* Run the migrations.
10			*
11			* @return void
12			*/
13			public function up()
14			{
15			Schema::create(config('mailman.storage.database.table'), function (Blueprint $table) {
16			$table->increments('id')->unsigned();
17
18			$table->string('message_id', 512);
19			$table->string('content_type', 64);
20
21			$table->enum('status', ['allowed', 'denied']);
22
23			$table->mediumText('from', 512);
			0 ignored issues – show Unused Code introduced 2016-04-12 16:51 UTC by Report Bug Copy Issue Report The call to `Blueprint::mediumText()` has too many arguments starting with `512`. 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. In this case you can add the `@ignore` PhpDoc annotation to the duplicate definition and it will be ignored. Loading history...
24			$table->mediumText('to', 512);
			0 ignored issues – show Unused Code introduced 2016-04-12 16:51 UTC by Report Bug Copy Issue Report The call to `Blueprint::mediumText()` has too many arguments starting with `512`. 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. In this case you can add the `@ignore` PhpDoc annotation to the duplicate definition and it will be ignored. Loading history...
25			$table->mediumText('reply_to', 512)->nullable();
			0 ignored issues – show Unused Code introduced 2016-04-12 16:51 UTC by Report Bug Copy Issue Report The call to `Blueprint::mediumText()` has too many arguments starting with `512`. 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. In this case you can add the `@ignore` PhpDoc annotation to the duplicate definition and it will be ignored. Loading history...
26
27			$table->mediumText('cc')->nullable();
28			$table->mediumText('bcc')->nullable();
29
30			$table->string('subject');
31			$table->mediumText('body');
32
33			$table->mediumText('instance');
34
35			$table->timestamps();
36			});
37			}
38
39			/**
40			* Reverse the migrations.
41			*
42			* @return void
43			*/
44			public function down()
45			{
46			Schema::drop(config('mailman.storage.database.table'));
47			}
48			}
49

qodeboy / laravel-mailman

GitHub Access Token became invalid

CreateMailmanMessagesTable::up() B last analyzed 2017-10-03 14:51 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

CreateMailmanMessagesTable::up() B
last analyzed 2017-10-03 14:51 UTC