ransome1 / sleek

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

Priority on new tasks is broken in 2.0.0-dev13 #528

Closed swantzter closed 11 months ago

swantzter commented 11 months ago

Bug Report

IMPORTANT: Please follow this template strictly when reporting bugs. Providing detailed and accurate information helps the development team to understand and address the issue effectively.

App Version: 2.0.0-dev13

Platform: Windows

Installation Method: Direct Download

Bug Description: a) Writing priority in the "main" input field clears the input field b) Setting priority using the dropdown adds duplicate priority to the "main" input field

Steps to Reproduce:

a)

  1. Open the dialog to create a new task
  2. Type "(A) "
  3. The input field will be cleared

b)

  1. Open the dialog to create a new task
  2. Select priority A in the priority dropdown
  3. The input field will be filled in with "(A) (A) "

Expected Behavior: a) The input field is not cleared and I can continue typing the TODO b) Only one (A) should be prepended

Actual Behavior: a) The input field is cleared, (and the priority dropdown is not changed) b) The input field is prepended with "(A) (A) "

Additional Information:

Screenshots:

System Information:

Reproducibility:

Impact:

Workaround:

ransome1 commented 11 months ago

This is fixed by now, but let me to way more refactoring. Should be available in the next developer preview.

ransome1 commented 11 months ago

@swantzter same here: https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev14

swantzter commented 11 months ago

-dev14 solves this

I note that it would be neat if the priority dropdown updated based on what you type in the input field, similar to how the input field updates if you change the priority dropdown, but that's separate from this bug

ransome1 commented 11 months ago

@swantzter I agree, could be low priority enhancement. But if that will be implemented, the same thing must apply to all other available attributes. Feel free to open up a feature request and I'm happy to add it to the backlog.