search

ransome1 / sleek

todo.txt manager for Linux, Windows and MacOS, free and open-source (FOSS)
https://github.com/ransome1/sleek/wiki
MIT License
1.34k stars 104 forks source link

appendStartDate not working any more #432

Closed dlaidig closed 1 year ago

dlaidig commented 1 year ago

Is it an actual bug? Yes

Did you check if the bug has already been reported? Yes

Describe the bug Recently the creation data is not saved in new entries any more. In my user-preferences.json I see that "appendStartDate": true is still set.

To Reproduce Steps to reproduce the behavior:

  1. Set appendStartDate to true
  2. Create new entry
  3. Check if todo.txt contains the creation date.

Do you see any error entries in sleeks developer tools? Should not be relevant.

Desktop (please complete the following information):

ransome1 commented 1 year ago

@dlaidig thanks for reporting this. Could you please check, if this feature does work again in https://github.com/ransome1/sleek/releases/tag/v1.2.9-rc.1

dlaidig commented 1 year ago

I was already about to write that it does not seem to have changed at all. Then I noticed it actually now works when creating issues via the dialog but not when using the "add as todo" button in the search bar (which I end up doing most of the time).

ransome1 commented 1 year ago

@dlaidig mmhh that's odd, let me look into it again.

dlaidig commented 1 year ago

Oh, and it totally does seem to break setting priorities in the dialog, either by typing "(A)" manually or by using the controls. The date is put before the priority, and then the priority is interpreted as text. After some iterations of trying to change the priority, I ended up with 2022-11-01 (A) 2022-11-01 (A) 2022-11-01 (A) test issue

ransome1 commented 1 year ago

I think I have to admit, that fixing this will be an ugly workaround. The root cause for this issue lies is the library, that parses the string into todo.txt objects. There is rewrite of this particular library going on at the moment and as soon as the it has been released, this issue will be fixed. As for now I won't continue working on fixing it, but the solution for this is near.

github-actions[bot] commented 1 year ago

This is an automated response. We acknowledge your report, and we appreciate your engagement. However, as there has been no recent activity in this thread, it has been marked as stale. If you have any further feedback or if the matter is still relevant, please do not hesitate to respond. Otherwise, this thread will be automatically closed in 15 days from now.

dlaidig commented 1 year ago

Glad to see that you are still working on sleek, @ransome1. I'm looking forward to test v2.0 when it is a bit further along. :)

I think this issue is still very much relevant and should be kept open.

ransome1 commented 1 year ago

Available in https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev9