feat(logs): colorize log lines using structured severity field#144
Merged
feat(logs): colorize log lines using structured severity field#144
Conversation
Replace the regex-based log level parser with direct use of the severity field from the structured ServiceLogEntry. Colorization now applies to the full log line based on the severity value rather than scanning the message text for embedded level tokens. Removes the logLevelRegex and colorizeLogLine helpers entirely.
Use the API-provided severity field to find and color just "SEVERITY:" within the message rather than the whole line. This avoids coloring the full line (which is hard on the eyes) while still being more precise than the old regex — no false matches when a severity word appears in the body.
AdrianLC
force-pushed
the
adrian/logs-severity-colorize
branch
from
d2f4f86 to
388311c
Compare
nathanjcochran
approved these changes
Apr 10, 2026
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
2 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.
Summary
severityfield from the structuredServiceLogEntryERROR:) is colorized within the line — not the full line — preserving the original behaviour that's easier on the eyes across different terminal color schemesWARNINGorERROR), whereas now only the actual severity of that log entry is colorizedMerge order
Depends on #143 (which introduces the structured
ServiceLogEntrywith theseverityfield). Merge that first.