fix(results): hide Scope config row when it equals the task's default#1101
Draft
gregmagolan wants to merge 1 commit into
Draft
fix(results): hide Scope config row when it equals the task's default#1101gregmagolan wants to merge 1 commit into
gregmagolan wants to merge 1 commit into
Conversation
The Configuration line on gazelle and format status surfaces always rendered the Scope row — including `Scope: all` on gazelle (default `all`) and `Scope: changed` on format (default `changed`). That's just noise; the user only cares when they deviated from the default. Now the row only renders when the scope value differs from the task's default. Non-default scope (and the `changed — N changed dirs` count suffix it carries on gazelle) is unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✨ Aspect Workflows Tasks📅 Tue May 19 11:57:10 UTC 2026 ✅ 16 successful tasks
⏱ Last updated Tue May 19 12:03:27 UTC 2026 · 📊 GitHub API quota 1,552/15,000 (10% used, resets in 52m) |
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.
The Configuration line on gazelle and format status surfaces always
rendered the Scope row — including
Scope: allon gazelle (defaultall) andScope: changedon format (defaultchanged). That'sjust noise; the user only cares when they deviated from the default.
The fix threads a per-task
_DEFAULT_SCOPEconstant into each task's_config_itemsand suppresses the row when the value equals thedefault. The non-default rendered case (and the
changed — N changed dirscount suffix it carries on gazelle) is unchanged.Changes are visible to end-users: yes
Suggested release notes
Scope: <default>Configuration row forgazelleandformat. The row still renders when the user picked a non-default--scope.Test plan
test-gazelle-template-snapshots: scenarios 1–12 now omit the Scope row (defaultall); 13–15 still render it (non-defaultchanged).test-format-template-snapshots: scenarios 1, 2, 4–9, 11–14 now omit the Scope row (defaultchanged); 3 and 10 still render it (non-defaultall).