Proposal: Integrate with Laravel 5.5 spatial fields migrations

[grimzy]

Proposal: Integrate with Laravel 5.5 spatial fields migrations

[xfudox]

@bkoch31 I found no official "solution" to this, but looking here you can see Eloquent already support spatial data types like point, multipoint and so on, so I'm using standard Blueprint class in migration with grimzy SpatialTrait in model and it gives no errors.

I tought that independently from how I create a table with a point field, it will sitll be a point field, so the SpatialTrait will be able to read and write to it correctly in the end.

[xfudox]

I agree with you, I'm making some tests but i keep receiving

TypeError: [...] {closure}() must be an instance of Grimzy\LaravelMysqlSpatial\Schema\Blueprint, instance of Illuminate\Database\Schema\Blueprint given

It would be fantastic to use Eloquent spatial fields with your SpatialTrait.

[bkoch31]

I agree with you, I'm making some tests but i keep receiving

TypeError: [...] {closure}() must be an instance of Grimzy\LaravelMysqlSpatial\Schema\Blueprint, instance of Illuminate\Database\Schema\Blueprint given

It would be fantastic to use Eloquent spatial fields with your SpatialTrait.

@xfudox did you find a workaround for this? Writing tests with the same error as well.