Don't pass urgency:0 to taskwarrior 2.5.2 for task modify #142
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When modifying a task in taskwarrior 2.5.2 it was returning this error: The 'urgency' attribute does not allow a value of '0'. The solution is to drop the urgency argument if the value is 0 when calling task modify.
|
For what it's worth, I'm fairly sure the urgency field is calculated anyway (and thus immutable) -- we should probably never be sending that in our command. |
|
Yeah, I recently stumbled upon the same issue, explicitly removing the |
jayvdb
approved these changes
Jul 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When modifying a task in taskwarrior 2.5.2 it was returning this error:
The 'urgency' attribute does not allow a value of '0'.
The solution is to drop the urgency argument if the value is 0 when calling task modify.