We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Out of nearly 400 art installation entries, all but one were encoded in the JSON data as strings. One entry was encoded as a number.
To Reproduce Get the API response: https://api.burningman.org/api/v1/art?year=2018 Search for 3.14 examine the entry's "name" field
Expected behavior Should be a string, ie "name": "3.14", Is actually encoded as a number: "name": 3.14,
The text was updated successfully, but these errors were encountered:
Thanks for pointing this out. We are working on fixing this. It exposes a more general issue with the validation of types in the returning JSON.
Sorry, something went wrong.
I suggest ensuring all names are encoded as strings, not just art installations.
same for camps. 2 camps have a numeric name:
No branches or pull requests
Describe the bug
Out of nearly 400 art installation entries, all but one were encoded in the JSON data as strings. One entry was encoded as a number.
To Reproduce
Get the API response: https://api.burningman.org/api/v1/art?year=2018
Search for 3.14
examine the entry's "name" field
Expected behavior
Should be a string, ie "name": "3.14",
Is actually encoded as a number: "name": 3.14,
The text was updated successfully, but these errors were encountered: