You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the library and I have used it in a few projects now. Up till recently I had no issues with it, but now things changed.
I am working on a project where files that are bigger than 10Mb would get received and I would like to transform those to corresponding objects in PHP. This library uses the default json_decode implementation, which works nice, but for big objects is a no go because of memory consumptions.
Even worse is that the current code base uses @json_decode() to suppress any error messages with malformed json, so if php terminates the process because of no enough memory the developer would have no clue on what happened.
Seems like there are solutions around. For example:
I love the library and I have used it in a few projects now. Up till recently I had no issues with it, but now things changed.
I am working on a project where files that are bigger than 10Mb would get received and I would like to transform those to corresponding objects in PHP. This library uses the default
json_decode
implementation, which works nice, but for big objects is a no go because of memory consumptions.Even worse is that the current code base uses
@json_decode()
to suppress any error messages with malformed json, so if php terminates the process because of no enough memory the developer would have no clue on what happened.Seems like there are solutions around. For example:
I would love it if we come up with a way of using one of those approaches in the default visitor. Do you guys have any thoughts on this?
The text was updated successfully, but these errors were encountered: