-
Notifications
You must be signed in to change notification settings - Fork 24
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
Adapter returns stringified array #291
Comments
What exact endpoint are you using? |
I am using the "preview" endpoint ( |
Well, this is currently somehow by design (our internal events use this format too) and also because the Adapter is written in Java. As Java and JPA do not natively support JSON, we are storing the Might be worth keeping this in mind when we are discussing #283 in the next meeting. |
Exactly, we stored the data as a string because this was the simplest solution regarding persistence. |
When requesting data using the Adapter, we get a response like this:
Expected result:
The "data" field should be an actual array.
Actual result
The "data" field is currently a string. So you need to run
JSON.parse()
in order to get the actual data.The text was updated successfully, but these errors were encountered: