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
I often add many duplicate items because I'm not sure if the button has been triggered, or if my Ctrl+Enter hotkey has been triggered. This is after I've typed out a new todo in the search bar, and then click "+ Add as todo".
Impact on the interface
Improves the interface and UX.
Potential Alternatives/Additions
It may be good to prevent duplicate items from being added back-to-back. I never want to add the exact same item twice in a row, so it might be good to warn/indicate/prevent that action.
The text was updated successfully, but these errors were encountered:
I understand the issue at hand. And technically speaking it should not be an issue to avoid the creation of a duplicate.
My workflow is usually that I type in the string, I would like to add as a todo. Since this particular string does usually not yield any search results (which would indicate a possible duplicate), sleek's body is empty. If I know click on Add as todo, the formerly empty body will be filled with exactly that one new todo I just created. And since the body was empty before, I'm sure there is no duplicate.
I run into the same issue. When adding from the filterline, the filter does not seem to be updated. The duplicates only appear when you empty the filter line once and fill it again.
Feature Request
What problem does it solve?
I often add many duplicate items because I'm not sure if the button has been triggered, or if my Ctrl+Enter hotkey has been triggered. This is after I've typed out a new todo in the search bar, and then click "+ Add as todo".
Impact on the interface
Improves the interface and UX.
Potential Alternatives/Additions
It may be good to prevent duplicate items from being added back-to-back. I never want to add the exact same item twice in a row, so it might be good to warn/indicate/prevent that action.
The text was updated successfully, but these errors were encountered: