Gracefully handle not getting valid input for an ID in query params #4358
Labels
Type: Enhancement
This is an improvement of an existing thing (not a new thing, which would be a feature).
Comments
wes-otf
added
the
Type: Enhancement
|
very much an edge case, just came up a few times when staff were trying to work around #4357 |
frjo
pushed a commit
that referenced
this issue
Jan 31, 2025
Fixes #4357 & #4358. Multiple small fixes to the all submissions table, including: - Allowing for the selection of multiple rounds, leads, and funds while filtering - Updated display tags for filters to reflect multiple selections - Added template tag to get display names of users in filter tag display (leads + reviewers) - Added `scroll-auto` to remove the scroll bar gap on some of the submenus - Caps normalizations - Handling of non-int values in query params that use int ids - Added more translatable strings
|
Closed by #4360 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When an invalid
idis provided as a query param for the all submissions view (ie.?rounds=aa&fund=fghj), the server throws an error rather than notifying the user/ignoring the invalid inputThe text was updated successfully, but these errors were encountered: