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
Sorting functionality no longer works after the fix implemented for #6382 (invalid sort parameters causing a 500 status code). Currently, any sorting parameter provided results in an UnsupportedSortException, making sorting unusable.
Preconditions
The user is logged in, and the token is gotten.
Send the request with valid sort parameters (for instance "id").
Observe the response.
Actual result
The status code is 400 Bad Request.
Any sorting parameter causes an exception (UnsupportedSortException: INVALID_SORTING_VALUE), even if the parameters are valid.
Environment: Swagger
Reproducible: always
Build found: "commitHash": "2d94ac7fce116bc532e5f1dec5dd7def8bfa4859",
"commitDate": "20/01/2025 15:27:26"
Sorting functionality no longer works after the fix implemented for #6382 (invalid sort parameters causing a 500 status code). Currently, any sorting parameter provided results in an UnsupportedSortException, making sorting unusable.
Preconditions
The user is logged in, and the token is gotten.
Steps to reproduce
Actual result
The status code is 400 Bad Request.
Any sorting parameter causes an exception (UnsupportedSortException: INVALID_SORTING_VALUE), even if the parameters are valid.
Expected result
The status code is 200 Success.
User story and test case links
#1003
Labels to be added
"Bug", "API"
The text was updated successfully, but these errors were encountered: