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.
A natural thing to do when sorting task list is to sort by urgency. If two tasks have same urgency, then I am not sure how the order is calculated. But, imagine you have the following tasks and viewport:
where
$V
isurgency-,description+
. Suppose the two tasks have the same urgency. Imagine now that there are more chapters. In this case the listing would look like:This is obviously not the way it should be. The topmost tasks should be the ones that should be done first and chapter 10 should come after chapter 9. This is at least the assumption this PR makes. That in "series of tasks", i.e. multiple tasks sharing the same description except an ordinal number at the end, the sorting should be natural.
I am not sure this PR breaks anything. The test suite seems broken currently. Once fixed, I will add tests and address any edge cases.