-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
response()->json() fails as it incorrectly interprets spatial fields #34
Comments
@lukepower Can you please help me to reproduce the issue by forking this repo and creating a PR with a failing test? Or provide a link to a new Laravel repo that has this issue? |
@MatanYadaev Just came back from vacation, will do it asap. ��b1E�� ���%ǝ��? I guess something is wrong with the way I set up the whole package... |
That's the same bug as in #28, which I've still been unable to solve. |
This issue happens when someone wants to see changes of a record ( For example, In Nova 4 there is a feature to log all changes of model's records. |
Should be fixed in version 2. Please check it. |
Just FYI I'm using v2.2 and still getting a |
Hi @devinfd, please respect my time, if you want me to fix the issue, make it easy to me to reproduce it. It will be best if you'll create a fork of this repo with a failing test, or a Laravel app repo that has a broken endpoint. |
Of course @MatanYadaev. I'm am currently debugging my issue to make sure that it's an issue on my end. I made the above comment because in your previous comment you said "Please check it." So I thought you would want the feedback. Awesome package! Glad to see that it's well cared for. |
When returning a collection with some spatial fields in it (in our case, all Point's) like this:
return response()->json($res);
We get a 500 error on the server with "Malformed UTF-8 characters, possibly incorrectly encoded".
As soon as I null the spatial field in the DB, the error dissolves. It seemingly is unable to correctly create a json out of the field.
Using latest Laravel 9 and current master.
The text was updated successfully, but these errors were encountered: