Describe the bug
Report names containing the string -tom in them fail to render in the TUI, i.e. it maintains the previous report originally shown, but the active filter line does update.
To Reproduce
Steps to reproduce the behavior:
For instance with the following examples, everything works except for x-tom. The task CLI recognizes all of these and works correctly
report.tom.description=tom works
report.tom.columns=id,project,description,entry.age,due,urgency
report.tom.labels=ID,Project,Description,Age,Due,Urg
report.tom.sort=urgency-
report.tom.filter=status:pending
report.tom-x.description=tom-x works
report.tom-x.columns=id,project,description,entry.age,due,urgency
report.tom-x.labels=ID,Project,Description,Age,Due,Urg
report.tom-x.sort=urgency-
report.tom-x.filter=status:pending
report.x-to.description=x-to works
report.x-to.columns=id,project,description,entry.age,due,urgency
report.x-to.labels=ID,Project,Description,Age,Due,Urg
report.x-to.sort=urgency-
report.x-to.filter=status:pending
report.x-tom.description=x-tom fails
report.x-tom.columns=id,project,description,entry.age,due,urgency
report.x-tom.labels=ID,Project,Description,Age,Due,Urg
report.x-tom.sort=urgency-
report.x-tom.filter=status:pending
I have not reproduced it with the bundled test data yet. The issue seems independent of my task data because it is triggered by the report key string itself.
In my config, a report key containing -tom appears in the report list but cannot be searched/selected correctly in the TUI. Renaming the same report to a key without -tom fixes it, with the same columns, labels, sort, filter, and task data.
Observed matrix:
tom workstom-x worksx-t worksx-to worksx-tom failsw-tomo failsshadow-tomo-poly-ansatz failsstpa works with the same filter as shadow-tomo-poly-ansatz
All of the corresponding reports work through the task CLI.
I can try the bundled test data later, but the current evidence points to the report picker/search handling of report keys containing the substring -tom, rather than a task-data issue.
Environment (please complete the following information):
- Operating System: Mac
- Installation: homebrew
- taskwarrior-tui version: 0.27.0
- task version: 3.4.2
taskwarrior-tui --version
Additional context and information
Describe the bug
Report names containing the string -tom in them fail to render in the TUI, i.e. it maintains the previous report originally shown, but the active filter line does update.
To Reproduce
Steps to reproduce the behavior:
For instance with the following examples, everything works except for x-tom. The task CLI recognizes all of these and works correctly
I have not reproduced it with the bundled test data yet. The issue seems independent of my task data because it is triggered by the report key string itself.
In my config, a report key containing
-tomappears in the report list but cannot be searched/selected correctly in the TUI. Renaming the same report to a key without-tomfixes it, with the same columns, labels, sort, filter, and task data.Observed matrix:
tomworkstom-xworksx-tworksx-toworksx-tomfailsw-tomofailsshadow-tomo-poly-ansatzfailsstpaworks with the same filter asshadow-tomo-poly-ansatzAll of the corresponding reports work through the
taskCLI.I can try the bundled test data later, but the current evidence points to the report picker/search handling of report keys containing the substring
-tom, rather than a task-data issue.Environment (please complete the following information):
Additional context and information