-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Priority parsing #120
Comments
Yes, the parser will grab the last priority it finds, not the first. I agree it should grab the first leaving the rest as part of the task description. What version are you running by the way? |
Fixed and tested in master. Please re-open if you need to discuss more. |
Actually re-opening -- I did the same for projects, but I;m wondering if we should throw an error if multiple projects or priorities are supplied. I'm not sure yet, as I definitely have wanted to add things that look like a query in the description before. |
Definitely some parsing bugs around this. I propose we allow stuff like this after the
This currently yields the expected behavior. A task with priority P3 and the summary text "I parked my car on level P1 or was it P2" But if we add an illegal, non-existent priority, we get a strange result.
|
Hi,
this is a little strange behaviour when adding tasks with priorities:
this is not accepted but could conceivably be a task named "P2" with priority "P1".
this is accepted (it really should be illegal) but can you guess the resulting priority? It's P2.
The text was updated successfully, but these errors were encountered: