-
Notifications
You must be signed in to change notification settings - Fork 898
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
Allow operator characters on the RHS of filter #15534
Allow operator characters on the RHS of filter #15534
Conversation
Fixes an issue where filters with operator characters on the RHS would return 400s. This is because it parses the operator as the first one found anywhere in the filter. By taking a more LALR-ish approach, we can avoid this problem by parsing it as the first operator found in the string. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1365013
Checked commit imtayadeway@1a21138 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
@miq-bot assign @gtanzillo |
@miq-bot assign @abellotti |
LGTM !! Thanks @imtayadeway 🎵 |
@imtayadeway @abellotti can/should this be backported to Fine/Euwe branch? |
@simaishi it should be possible to backport this to Fine, but can't be easily backported to Euwe |
…n-rhs Allow operator characters on the RHS of filter (cherry picked from commit d9cd967) https://bugzilla.redhat.com/show_bug.cgi?id=1481296
Fine backport details:
|
…rators-on-rhs Allow operator characters on the RHS of filter (cherry picked from commit d9cd967) https://bugzilla.redhat.com/show_bug.cgi?id=1481296
Fixes an issue where filters with operator characters on the RHS would
return 400s. This is because it parses the operator as the first one
found anywhere in the filter. By taking a more LALR-ish approach, we
can avoid this problem by parsing it as the first operator found in
the string.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1365013
@miq-bot add-label bug, api
@miq-bot assign @abellotti