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
We try to use gbox as a reverse proxy in between a headless pimcore graphql instance and a React frontend. We get errors from gbox for queries that work perfectly fine on the normal backend. It seems like the query parser within gbox is the one that throws this error even before the query is sent to the backend. The error reported is:
internal: json: error calling MarshalJSON for type json.RawMessage: invalid character 'c' looking for beginning of value
It seems like the parts fullpath(thumbnail: "content") are the ones triggering the error. While it works perfectly fine as long as there is only one thumbnail query, as soon as we add the second one the error comes up.
Any suggestions how we can solve the problem (except stripping out the thumbnail queries ;) )
If this question should not be here as we are not even sure that it is a bug on gbox, feel free to close the issue.
Thanks
The text was updated successfully, but these errors were encountered:
We try to use gbox as a reverse proxy in between a headless pimcore graphql instance and a React frontend. We get errors from gbox for queries that work perfectly fine on the normal backend. It seems like the query parser within gbox is the one that throws this error even before the query is sent to the backend. The error reported is:
internal: json: error calling MarshalJSON for type json.RawMessage: invalid character 'c' looking for beginning of value
The Query we are sending is:
It seems like the parts
fullpath(thumbnail: "content")
are the ones triggering the error. While it works perfectly fine as long as there is only one thumbnail query, as soon as we add the second one the error comes up.Any suggestions how we can solve the problem (except stripping out the thumbnail queries ;) )
If this question should not be here as we are not even sure that it is a bug on gbox, feel free to close the issue.
Thanks
The text was updated successfully, but these errors were encountered: