You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 18, 2021. It is now read-only.
Context:
I have added a new filter to my dasboard, and tried to apply it to my widgets.
When this filter is the only one applied to the query, everything works fine, but the issue comes when I add this filter to a previous one (so the widget would take 2 filters)
which seems to be telling me that, if the first filter has not been selected, the return false; is executed, which will ignore the second filter, which might be set.
Possible solution:
moving every to forEach, or always use return true;?
Happy to make a PR for this one depending on feedbacks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Context:
I have added a new filter to my dasboard, and tried to apply it to my widgets.
When this filter is the only one applied to the query, everything works fine, but the issue comes when I add this filter to a previous one (so the widget would take 2 filters)
Here is an example of the query:
Now looking at
ApplicationInsights/Query
, I found this piece of code:which seems to be telling me that, if the first filter has not been selected, the
return false;
is executed, which will ignore the second filter, which might be set.Possible solution:
moving
every
toforEach
, or always usereturn true;
?Happy to make a PR for this one depending on feedbacks!
The text was updated successfully, but these errors were encountered: