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
Given an API request When I perform it in a web browser (Google Chrome, Firefox, Safari) Then I expect to get a parsable JSON, which is understood by plugin https://github.com/callumlocke/json-formatter for example
βοΈ Engineering Details
In my Google Chrome browser on macos the request comes with Accept header value "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.9"
I guess we should make the API return application/json when such Accept header is received. Maybe we should identify application/json as text/html.
The text was updated successfully, but these errors were encountered:
π§βπ¬ User Persona(s)
πͺ Motivation
...so that I can see well defined json and that possibly my browser plugin help me to explore it.
π Additional Details
A plugin which should work on the API response is https://github.com/callumlocke/json-formatter
βοΈ Acceptance Criteria
Given an API request
When I perform it in a web browser (Google Chrome, Firefox, Safari)
Then I expect to get a parsable JSON, which is understood by plugin https://github.com/callumlocke/json-formatter for example
βοΈ Engineering Details
In my Google Chrome browser on macos the request comes with Accept header value "text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.9"
I guess we should make the API return application/json when such Accept header is received. Maybe we should identify application/json as text/html.
The text was updated successfully, but these errors were encountered: