Skip to content

Commit f091bc1

Browse files
committed
docs(lint): stop re-citing an issue number that resolves in neither repo
The #11385 narrowing comment added by this PR cited `#10262` for the fan-out block. Measured on the REST API with a token: `#10262` answers HTTP 404 in both objectstack-ai/objectstack and objectstack-ai/objectui; lit control on the same instrument in the same act, `#7079` answers 200 in both. So the number points at nothing and this PR should not add a fresh pointer to it. The comment now names the block instead, and says what was measured. The nine pre-existing `#10262` citations in this file are left exactly as found — they predate this card and correcting them is not its scope. Claude-Session: https://claude.ai/code/session_01JbZnqu8bt6YqfJsr9vaFb3 Co-authored-by: Claude <noreply@anthropic.com>
1 parent aa3e6d4 commit f091bc1

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

‎packages/lint/src/lint-liveness-properties.test.ts‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -914,7 +914,11 @@ describe('lintLivenessProperties', () => {
914914
});
915915

916916
// ⚠️ THE FIELD CASE LOST ITS SUBJECT (#19187), and unlike the fan-out
917-
// (#10262) the code path went with it: `field.relatedListFilter` was the
917+
// block at the bottom of this file the code path went with it (that block's
918+
// own `#10262` citation is left as found; the number resolves in NEITHER
919+
// objectstack nor objectui — measured, with `#7079` answering 200 on the
920+
// same instrument — so this comment names the block rather than re-citing
921+
// it): `field.relatedListFilter` was the
918922
// ONE `authorWarn` row on `field.json` at any depth, so flipping it `live`
919923
// empties `loadWarnMap(dir, 'field')` and `lintLivenessProperties` skips the
920924
// whole field loop on `if (fieldWarn.size > 0)` — the `if (!isRecord(field))

0 commit comments

Comments
 (0)