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
When using the /shells endpoint to get all shells there is an error stating that the cursor and idShort query parameters are not set.
In my opinion, this behaviour is absolute nonsense, especially because the idShort query parameter cannot be empty and needs to be a perfect match to return any result at all.
This is the returned error body: { "errors": { "cursor": [ "The cursor field is required." ], "idShort": [ "The idShort field is required." ] }, "type": "https://tools.ietf.org/html/rfc9110#section-15.5.1", "title": "One or more validation errors occurred.", "status": 400, "traceId": "00-0792b1f9467fdff4ed7eb4c2f79152dd-340538d57374bead-00" }
To reproduce
Just use the /shells GET without query parameters
Screenshots
No response
Expected Behaviour
All Shells in the server should be returned.
Version
v0.3.1.40-aasV3-alpha-latest
Operating System
Windows 10
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
@BohnSeb thanks for the issue.
We currently have some issues we're trying to fix asap. I look into it shortly. There will be a new prerelease soon, that should improve this topic
Contact Details
No response
Describe the bug
When using the /shells endpoint to get all shells there is an error stating that the cursor and idShort query parameters are not set.
In my opinion, this behaviour is absolute nonsense, especially because the idShort query parameter cannot be empty and needs to be a perfect match to return any result at all.
This is the returned error body:
{ "errors": { "cursor": [ "The cursor field is required." ], "idShort": [ "The idShort field is required." ] }, "type": "https://tools.ietf.org/html/rfc9110#section-15.5.1", "title": "One or more validation errors occurred.", "status": 400, "traceId": "00-0792b1f9467fdff4ed7eb4c2f79152dd-340538d57374bead-00" }
To reproduce
Just use the /shells GET without query parameters
Screenshots
No response
Expected Behaviour
All Shells in the server should be returned.
Version
v0.3.1.40-aasV3-alpha-latest
Operating System
Windows 10
Relevant log output
No response
The text was updated successfully, but these errors were encountered: