You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 13, 2023. It is now read-only.
On second thought, it's not possible with a comma and the end of the line character, for example Get milk, eggs, flour and baking powder would break the expectation that you are able use comma characters in the task description. So escaping seems to be the only way to use the comma end of line string anchors. Perhaps a way to denote a datetime in a string Get milk {tommorow}, what do you think?
This definitely seems to be like something that is going to be different for every user. You could use a different delimiter, but that has the same issue with whatever that one is. Something like [tomorrow] would require some rework to get used to that but would work. So would having to put in "due " and parsing for "due" (then if it's not present, there would be no date).
I'm not sure how everyone else uses it or types things in so not sure what may be the best though. The official app searches for dates and parses those, and if you enter multiple dates it only counts the last one entered.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
I often need to create a task that has a comma within it, but that won't work because the workflow parses any "," as a date delimiter
Describe the solution you'd like
Search from the end and parse only the final "," instead of all ","
Additional context
For example, a todo such as "Call Amy, John, and Jim, oct 10" should parse correctly to be due Oct 10 with a task of "Call Amy, John, and Jim".
This does raise the question of what about if I don't want a due date - is there a workaround such as entering it with quotes or brackets?
The text was updated successfully, but these errors were encountered: