Skip to content

fix: underline grammar-backed keys instead of recoloring them (#467)#481

Open
SJrX wants to merge 1 commit into
issue-345-11from
issue-345-12
Open

fix: underline grammar-backed keys instead of recoloring them (#467)#481
SJrX wants to merge 1 commit into
issue-345-11from
issue-345-12

Conversation

@SJrX

@SJrX SJrX commented Jun 21, 2026

Copy link
Copy Markdown
Owner

What

The key marker from #474 (GrammarEngineKeyAnnotator) tinted grammar-backed keys (Bond, Description, …) a distinct color. Having two different key colors was too distracting — especially on light themes. Switch it to a plain underline: the key keeps its normal color and just gets a subtle underline to signal "grammar-backed".

Stacked on #480 (issue-345-11).

Change

NEW_ENGINE_KEY now defaults to TextAttributes(effectType = LINE_UNDERSCORE) (gray underline, no foreground change) instead of DefaultLanguageHighlighterColors.METADATA. One-line behavioral change; the annotator still marks the same keys, just less loudly. Existing test (asserts the key gets the marker) still passes; full suite green.

Refs #467

🤖 Generated with Claude Code

The key marker (GrammarEngineKeyAnnotator) tinted grammar-backed keys with a distinct
color; having two key colors was too distracting, especially on light themes. Switch it
to a plain underline so the key keeps its normal color and the grammar marker is subtle.

Refs #467

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Test Results

1 142 tests  ±0   1 142 ✅ ±0   47s ⏱️ -1s
  303 suites ±0       0 💤 ±0 
  303 files   ±0       0 ❌ ±0 

Results for commit 320439c. ± Comparison against base commit 23baad8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant