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
An example of this is with /users/{id} - making use of the ID parameter causes a 404:
This is because the user's input isn't transmitted into the request URL (this can be seen in the above screenshot). Fixing this issue is just a case of changing the name of the parameter in the Swagger docs (in the endpoint files) so that it uses id rather than ID. Swagger is case sensitive, as per: https://swagger.io/docs/specification/describing-parameters/#path-parameters
Other endpoints that utilise this ID parameter should also be checked and corrected where needed.
The text was updated successfully, but these errors were encountered:
- Swagger is case sensitive when using parameters
- This change means endpoints with an ID parameter (e.g. /users/{id}) will now work using the Swagger UI user input for said ID
An example of this is with
![image](https://user-images.githubusercontent.com/32678030/84263460-709a9d80-ab17-11ea-9060-fac7d404166e.png)
/users/{id}
- making use of the ID parameter causes a 404:This is because the user's input isn't transmitted into the request URL (this can be seen in the above screenshot). Fixing this issue is just a case of changing the name of the parameter in the Swagger docs (in the endpoint files) so that it uses
id
rather thanID
. Swagger is case sensitive, as per: https://swagger.io/docs/specification/describing-parameters/#path-parametersOther endpoints that utilise this ID parameter should also be checked and corrected where needed.
The text was updated successfully, but these errors were encountered: