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 Apr 12, 2024. It is now read-only.
I filter from an input an array on a specific field.This field is an array. Sometimes, i have values, sometimes not.
The initial state, I see all items of this array. I type something in the input, the filter filters the field which expects with the input. When my input is empty, it shows all items where the field isn't empty.
I'm expected to get the same behaviour when I initialize my application.
This is expected behavior. It happens because initially the expression is undefined, but when you clear the field it is an empty string (and filtering with undefined behaves differently than filtering with the empty string).
See #12060 for more context and possible work-arounds.
I filter from an input an array on a specific field.This field is an array. Sometimes, i have values, sometimes not.
The initial state, I see all items of this array. I type something in the input, the filter filters the field which expects with the input. When my input is empty, it shows all items where the field isn't empty.
I'm expected to get the same behaviour when I initialize my application.
http://plnkr.co/edit/d99r5yPDEKqmGIGM8OqP?p=preview
I found a workaround to set the filtered field to undefined when the input is empty
http://plnkr.co/edit/nG951XNg43tUcj0IkRvN?p=preview
The text was updated successfully, but these errors were encountered: