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
To me, it seems like applying a filter does each in order now. For example, if I select tracker -> include -> exclude, it first completely gets all that should be included, then all that should be excluded. Is it not debounced? Does it not wait until the menu is closed?
This is particularly bad if it does this with category additions/removals. Imagine if some items you have selected are in a category, but not all. The state is -, and adding them you want to get to +, but have to go through , meaning it will first try to remove all selected items before adding them.
This makes the bug where removing items from a category crashes (after processing some items, so you have to repeat the process) to also happen with ADDING items.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
To me, it seems like applying a filter does each in order now. For example, if I select tracker -> include -> exclude, it first completely gets all that should be included, then all that should be excluded. Is it not debounced? Does it not wait until the menu is closed?
, meaning it will first try to remove all selected items before adding them.
This is particularly bad if it does this with category additions/removals. Imagine if some items you have selected are in a category, but not all. The state is
-
, and adding them you want to get to+
, but have to go throughThis makes the bug where removing items from a category crashes (after processing some items, so you have to repeat the process) to also happen with ADDING items.
Has anyone else noticed this, or am I crazy?
Beta Was this translation helpful? Give feedback.
All reactions