New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix naming a filter offset or limit breaks dashboards #40821
Fix naming a filter offset or limit breaks dashboards #40821
Conversation
|
c481f75
to
d4582c1
Compare
This middleware shouldn't throw exceptions when `limit` or `offset` query parametesr aren't integers.
d4582c1
to
3fb394c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just want to make sure I understand the solution fully here — we're just not throwing an error anymore if limit
or offset
query params are passed in that can't be parsed? But as long as they're numerical, we'll still parse & bind them as usual?
Yes, sorry - my PR message was wrong because it described another approach which I also implemented but ended up removing from this PR. |
@johnswanson Did you forget to add a milestone to the issue for this PR? When and where should I add a milestone? |
Don't throw an exception from that middleware if it's sent a
limit
oroffset
query param that isn't an integer.#38008