Skip to content

Commit 90c2b5d

Browse files
committed
test(lint): give the new battery's annotation case a name of its own
Two batteries carried the same case name, so a red on either printed a line that did not say which rule stopped working -- the exact ambiguity the battery roster exists to remove. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019RfFHiRCSs3JXLK4cwcfox
1 parent 5757baa commit 90c2b5d

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

scripts/check-partof-closing-keyword.mjs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1074,7 +1074,7 @@ function selfTest() {
10741074
EXIT_CLEAN,
10751075
);
10761076
t(
1077-
'a number already declared Part of is RULE 1s row: RULE 3 does not double-report it',
1077+
"a number already declared Part of is RULE 1's row: RULE 3 does not double-report it",
10781078
h21NegatedClosingKeyword({ body: 'Part of #8131 — this does not close #8131 yet.' }),
10791079
null,
10801080
);
@@ -1109,7 +1109,7 @@ function selfTest() {
11091109
negatedText.includes('Backticks are NOT the escape in a'),
11101110
true,
11111111
);
1112-
t('the failure is annotated for the GitHub UI', negatedText.includes('::error::'), true);
1112+
t('the RULE 3 failure is annotated for the GitHub UI', negatedText.includes('::error::'), true);
11131113

11141114
// The floor runs BEFORE the verdict below, so a success line can only be
11151115
// printed by a run in which every declared battery registered its cases.

0 commit comments

Comments
 (0)