Eloquent `point` field type data triggers "Unexpected end of JSON input"
Is anyone using the
Dropping the database column and disabling the custom model setters that set the data based on field inputs resolves the issue, so it would seem as first glance to be related to the way the encoded point data is handled by the JSON encoder. As such, I'm wondering if anyone has encountered anything similar before I go bug hunting/try and create a stripped back project to illustrate the issue.
I suspect this may be a Livewire v3 issue rather than a Filament one, but I thought I'd ask here first.
point Eloquent field/attribute type in any of their models that have Filament resources? I've a resource that makes use of this which is failing with an "Unexpected end of JSON input" console error when attempting to view/edit a model which contains encoded point data. Attempting to create a new instance of the model initially works as expected, up until the point that the newly created model with the encoded data present is loaded.Dropping the database column and disabling the custom model setters that set the data based on field inputs resolves the issue, so it would seem as first glance to be related to the way the encoded point data is handled by the JSON encoder. As such, I'm wondering if anyone has encountered anything similar before I go bug hunting/try and create a stripped back project to illustrate the issue.
I suspect this may be a Livewire v3 issue rather than a Filament one, but I thought I'd ask here first.
