fix: Subprojects not being colored#769
Draft
rtim75 wants to merge 1 commit into
Draft
Conversation
rtim75
changed the title
rtim75
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #768
DISCLAIMER: I did use AI to analyze existing tui and taskwarrior codebases to compare both behaviours.
In spirit of this mr I tried to replicate original taskwarrior behaviour which is left-most match.
Test data that I used to verify can be found here: https://github.com/rtim75/taskwarrior-testdata
This makes tui to check if task's project starts with the project specified in the rule.K
Resulting behaviour can be seen on the screenshot below:
