I created a task from the “Add A Task…” field and the QAM functionality parsed a date from the entry that was not intended.
I entered the string: ‘Renovation - 2nd Floor Bath’
Vikunja created a task called ‘Reation - Floor Bath’ with a due date of November 2nd.
I understand that this field is supposed to parse dates alongside task titles, however given that the NOV which was parsed as november was in the middle of a word, my first reaction is that this is unintended behavior.
This should work - can you reproduce this on the demo?
Sorry, I had to leave the house. So I’ve tested just now on mobile, and it appears to still be an issue on the demo.
The result is second from the bottom.
Some additional testing:
I ran the test again (in the demo) from my PC, like I did last night from mobile. Same result. I then tried to just create a task called ‘Renovate’. This did not get assigned a date and none of the letters in the title were removed.
Then, I tried two strings that were similar to the ones I’d used in my OP description, crafted to potentially trip the issue, but otherwise meaningless.
’Remark - 13th floor’ and ‘13th floor - remark’
Both showed the behavior I’m inquiring about.
Managed to reproduce, this will be fixed in this PR: fix(quick-add-magic): prevent parsing partial keywords in words by kolaente · Pull Request #2140 · go-vikunja/vikunja · GitHub
Once that’s merged, please check with the next unstable build or on the demo if your problem was fully solved.
Very cool. Thank you for your attention to this.
I’ve tested in the demo and I can confirm I no longer see the issue. At present, I’ll wait for the next release to mod my local hosted instance.
Incidentally, is it better for you and your team to have bug candidates and feature requests posted here? Or is it more optimal to post issues directly to github?
Thanks again!!
Both are fine! Feature discussions maybe better here in the forum, but I read everything everywhere.
