-
Notifications
You must be signed in to change notification settings - Fork 23
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: query specification - always treat 'in','not-in' filter values as an array #439
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #439 +/- ##
=======================================
Coverage 83.20% 83.21%
=======================================
Files 62 62
Lines 4168 4170 +2
=======================================
+ Hits 3468 3470 +2
Misses 547 547
Partials 153 153 ☔ View full report in Codecov by Sentry. |
if valueSet { | ||
return filter, fmt.Errorf(multipleValuesError) | ||
} | ||
filter.Value = vb | ||
filter.Value = v | ||
} | ||
|
||
if filter.Op == honeycombio.FilterOpIn || filter.Op == honeycombio.FilterOpNotIn { |
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.
I understand we're doing "it's an in,not-in filter" things in two places at the moment, but this second check is a function of the deprecated value_*
options. Once they're removed we can do this all in one place above
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.
🎉 looks great!
in
, andnot-in
filter values should always be treated as an array. This allows for the possibility of filters likeapp.mything.id not-in 38374