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'm frustrated when make a typo in a parameter and I get a result from the API anyway but without my parameter being understood.
π§βπ¬ User Persona(s)
Data user
πͺ Motivation
...so that I can quickly spot wrong usage of the API
π Additional Details
Check tht there is not a extensibility motivation for supporting extra parameter silently. However I believe this is true at the specification level (the specification is extensible) but should not be true at the implementation level (the implementation is limited and should be explicit about it)
Acceptance Criteria
Given deployed server When I perform a request curl http://{server-host}/product?keyword=thing Then I expect i expect an error 400, with a text message saying parameter 'keyword' is not supported by the API
βοΈ Engineering Details
Provide some design / implementation details and/or a sub-task checklist as needed. Convert issue to Epic if estimate is outside the scope of 1 sprint.
The text was updated successfully, but these errors were encountered:
Checked for duplicates
No - I haven't checked
Related problems
I'm frustrated when make a typo in a parameter and I get a result from the API anyway but without my parameter being understood.
π§βπ¬ User Persona(s)
Data user
πͺ Motivation
...so that I can quickly spot wrong usage of the API
π Additional Details
Check tht there is not a extensibility motivation for supporting extra parameter silently. However I believe this is true at the specification level (the specification is extensible) but should not be true at the implementation level (the implementation is limited and should be explicit about it)
Acceptance Criteria
Given deployed server
When I perform a request curl http://{server-host}/product?keyword=thing
Then I expect i expect an error 400, with a text message saying parameter 'keyword' is not supported by the API
βοΈ Engineering Details
Provide some design / implementation details and/or a sub-task checklist as needed. Convert issue to Epic if estimate is outside the scope of 1 sprint.
The text was updated successfully, but these errors were encountered: