carloea2 opened a new issue, #8147: URL: https://github.com/apache/texera/issues/8147
### What happened? Dashboard search silently accepts an unknown `orderBy` value and runs an unordered offset query. That can make pagination unstable instead of reporting invalid client input. Before: an unknown sort value returns 200 without an order clause. After: an unknown sort value returns 400, while documented sort values remain valid. ### How to reproduce? 1. Start the local development backend from main. 2. Request `GET /api/dashboard/publicSearch?resourceType=workflow&orderBy=Bogus`. 3. Observe HTTP 200. 4. Request the endpoint with `orderBy=NameAsc` and observe HTTP 200. ### Version/Branch 1.3.0-incubating-SNAPSHOT (main) ### Commit Hash (Optional) 98588bf2ab49aac65ebf002496eb057670e6fc07 ### What browsers are you seeing the problem on? Not browser-specific. ### Relevant log output The invalid value falls through to an empty order field list, so the query runs without ordering. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
