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

Creating a new todo while filtered by search will show all todo's #604

Closed
swantzter opened this issue Dec 7, 2023 · 14 comments
Closed

Creating a new todo while filtered by search will show all todo's #604

swantzter opened this issue Dec 7, 2023 · 14 comments
Labels
bug Something isn't working

Comments

@swantzter
Copy link

Bug Report

App Version: 2.0.3-rc.4
Platform: Windows
Installation Method: Direct download

Bug Description:
If you create a todo while you have filtered todos via the search bar, all todos will become visible (ignoring the search) once you save the todo

Steps to Reproduce:

  1. open search Ctrl+F
  2. Search for something
  3. Create a new task Ctrl+N, "(A) Test test", *add*

Expected Behavior:
the filtered list should keep showing, and the newly added todo should be included if matching the search

Actual Behavior:
All todos are shown

@swantzter swantzter added the bug Something isn't working label Dec 7, 2023
@ransome1 ransome1 moved this to Backlog in sleek 2.x Dec 12, 2023
@ransome1 ransome1 moved this from Backlog to Bugs in sleek 2.x Dec 14, 2023
@ransome1 ransome1 moved this from Bugs to In Progress in sleek 2.x Dec 18, 2023
@ransome1
Copy link
Owner

@swantzter can you please check if the latest pre-release solves this issue? https://github.com/ransome1/sleek/releases/tag/v2.0.4-rc.2

@swantzter
Copy link
Author

works!

@github-project-automation github-project-automation bot moved this from In Progress to Done in sleek 2.x Dec 19, 2023
@swantzter
Copy link
Author

@ransome1 I will say on an unrelated note, possibly related to the refactoring mentioned in the release notes that 2.0.4-rc.2 has a significantly worse launch time than previous versions on windows (~9s).

@ransome1
Copy link
Owner

This might be related to: #615

Is this just happening on the latest pre-release or also with the ones as described in 615?

@swantzter
Copy link
Author

Possible, I haven't experienced a delay like this on any earlier version, only 2.0.4-rc.2

@ransome1
Copy link
Owner

Quick questions:

Does this only happens on Windows, or are you experiencing the same thing on Linux too?

If only on windows: can I ask you to check if Windows Defender is up and running at the same time? I'm asking because I stumbled upon this: https://stackoverflow.com/questions/67982430/windows-defender-slowing-down-electron-startup

And at last: does it only affect the start up or also the actual usage of sleek once loaded?

@amariusz
Copy link
Collaborator

amariusz commented Jan 3, 2024

works!

Does it really work? I've checked rc.2, rc.3, rc.4 and the latest sleek-2.0.4 and it still resets the search after adding new item. The same also happens when I filter by entering text in search box and mark some item complete - all entries are shown.

@amariusz amariusz reopened this Jan 3, 2024
@github-project-automation github-project-automation bot moved this from Done to Bugs in sleek 2.x Jan 3, 2024
@ransome1
Copy link
Owner

ransome1 commented Jan 4, 2024

@swantzter @amariusz I think it has fallen victim to the ongoing refactoring. It should be fixed again in the next release.

@ransome1
Copy link
Owner

@amariusz could you please check if it now working as expected in https://github.com/ransome1/sleek/releases/tag/v2.0.6? if so, please feel free to close.

@amariusz
Copy link
Collaborator

Searching/filtering and completing tasks works properly now.
Searching/filtering and adding new tasks not so much, as clicking "Add as todo" seems to have no action. Although using Ctrl-N as a workaround works great.

Thank you!

@ransome1
Copy link
Owner

ransome1 commented Jan 12, 2024

You're right, one thing fixed, one thing broken. ;) I should really stop adding more features and instead focus on UI test automatization.

@ransome1
Copy link
Owner

@amariusz should be fixed in the latest pre-release: https://github.com/ransome1/sleek/releases/tag/v2.0.7-rc.1

@amariusz
Copy link
Collaborator

Thanks, it works fine now!

BTW It seems there's new feature that suggests to add filter or select the filter. It tends to get's in the way by obscuring the item(s) being filtered especially if there's one item showing and user is not interested in this functionality. Maybe there should be an option to disable it or initially present it in a form of icon like 🔻 that expands the filter menu after clicking it.
I suppose you expect the user to hit enter or escape after entering a query?

@ransome1
Copy link
Owner

Thanks, it works fine now!

BTW It seems there's new feature that suggests to add filter or select the filter. It tends to get's in the way by obscuring the item(s) being filtered especially if there's one item showing and user is not interested in this functionality. Maybe there should be an option to disable it or initially present it in a form of icon like 🔻 that expands the filter menu after clicking it. I suppose you expect the user to hit enter or escape after entering a query?

It is not yet a new feature, but a proof of concept for this feature request: #179 (comment)

I am collecting feedback over in that issue, could you post your feedback there as well? Then we have one source of truth.

To answer your question: This is the one thing about the feature I too dislike to far. During typing users would always see the Create Filter entry and bothers me as well. Of course a setting could disable it, but that does not yet solve the issue for the users, who want to use it. Let's see what we can do about it.

@github-project-automation github-project-automation bot moved this from Bugs to Done in sleek 2.x Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

3 participants