feat: add color coding for failed and broken commands #472
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
cbandera
force-pushed
the
feature/351-color-by-exit-code
branch
from
4561c19 to
198f1f6
Compare
Author
|
The diff has gotten somewhat polluted due to my refactoring and attempt to reduce code duplication. |
- Add support for different colors for recently failed commands (non-zero exit code) - Add support for different colors for broken commands (exit_factor == 0.0) - Update configuration to support new color settings in both light and dark modes The changes maintain backward compatibility while adding visual distinction between successful, recently failed, and always-failing commands.
…educes code complexity and duplication)
cbandera
force-pushed
the
feature/351-color-by-exit-code
branch
from
198f1f6 to
ba8cccf
Compare
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.
Adresses #351:
The changes maintain backward compatibility while adding visual distinction between successful, recently failed, and always-failing commands.