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
Describe the bug
A project's swagger documentation page (http://localhost:3000/api/) requires an ID for the GET/ endpoint (e.g. /api/users).
The same goes for sub-entities. For example, /api/users//comments requires an ID for the user and the comment. Thus you can't get all comments of a user.
Thanks @timhuebener we are looking into the fix. It seems like an issue with the swagger decorators and the way they handle child properties of the query objects. I will keep you updated
Describe the bug
A project's swagger documentation page (http://localhost:3000/api/) requires an ID for the GET/ endpoint (e.g. /api/users).
The same goes for sub-entities. For example, /api/users//comments requires an ID for the user and the comment. Thus you can't get all comments of a user.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The swagger documentation should not require an ID for GET many requests.
The text was updated successfully, but these errors were encountered: