Skip to content

How to disable force inject Grimzy\LaravelMysqlSpatial\Schema\Blueprint ? #109

Open
@4n70w4

Description

@4n70w4

Hi! Some problem. I already use another custom Blueprint. But your library force resolve own Blueprint. This breaks all my migrations. But I don’t need your blueprint at all. I would like it to not load automatically. I do not use Grimzy\LaravelMysqlSpatial\Schema\Blueprint in any of my migrations.

   Symfony\Component\Debug\Exception\FatalThrowableError  : Argument 1 passed to CreateConfirmationsTable::{closure}() must be an instance of App\Extend\Blueprint, instance of Grimzy\LaravelMysqlSpatial\Schema\Blueprint given, called in /var/www/app/vendor/laravel/framework/src/Illuminate/Database/Schema/Builder.php on line 166

  at /var/www/app/app/Services/ConfirmationService/migrations/2019_11_07_153504_create_confirmations_table.php:17
    13|      *
    14|      * @return void
    15|      */
    16|     public function up() {
  > 17|         Schema::create('confirmations', function (\App\Extend\Blueprint $table) {
    18|             $table->increments('id');
    19|             $table->morphsUnsignedIntegerWithoutIndex('confirmable');
    20|             $table->string('code');
    21|             $table->enum('status', Confirmation::STATUSES);

  Exception trace:

  1   CreateConfirmationsTable::{closure}(Object(Grimzy\LaravelMysqlSpatial\Schema\Blueprint))
      /var/www/app/vendor/laravel/framework/src/Illuminate/Database/Schema/Builder.php:166

  2   Illuminate\Database\Schema\Builder::Illuminate\Database\Schema\{closure}(Object(Grimzy\LaravelMysqlSpatial\Schema\Blueprint))
      /var/www/app/vendor/laravel/framework/src/Illuminate/Support/helpers.php:1124

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions