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
Yes, that seems to be the same issue, after some analysis it seems to "fail open" if a filter value is not existing.
I tried that just with a tag: If I search for a tag "foo", and it's not existing -> All devices are returned. If that tag exists, but is not assigned to any device-> empty result.
Seems to be a very easy to make error on the user side and a very unexpected behaviour.
Thanks for the report @sirtux and I tend to agree that this is unexpected behavior. I'd rather filters fail closed and not open, and we also need to try to make the filtering on field values a little more intuitive if we can.
Environment
Steps to Reproduce
Run the following GraphQL-Query:
{ devices(status: "Active") { name status { name } } }
Expected Behavior
I get a result set containing only the device with status "Active" or nothing because "Active" might be a nonexisting status.
Observed Behavior
I get a result set containing all devices
The text was updated successfully, but these errors were encountered: