Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show an indication that the "+ Add as todo" button has been triggered/clicked #641

Open
DeflateAwning opened this issue Jan 22, 2024 · 4 comments

Comments

@DeflateAwning
Copy link
Sponsor

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.

@ransome1
Copy link
Owner

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.

Does your workflow differ from this?

@Saturo78
Copy link

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.

@DeflateAwning
Copy link
Sponsor Author

I believe I'm seeing the same thing as @Saturo78

@andrei-a-papou
Copy link

andrei-a-papou commented Jan 26, 2024

Good point, I wanted to report the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

4 participants