Skip to content

Commit 6a7c779

Browse files
committed
fix(ui-merge): K4 — the self-repo URL sweep keeps no population floor once the extension's last links left
Merging main brought #27275, which deleted the vscode-extension package and with it the last two self-repo GitHub URLs in the tree, so the floor of 1 read 0. The extractor stays covered by its own selfRepoPath unit test. Claude-Session: https://claude.ai/code/session_01L9qibyMpJZ67jrDrno4jY1 Co-authored-by: Claude <noreply@anthropic.com>
1 parent d710e84 commit 6a7c779

1 file changed

Lines changed: 6 additions & 3 deletions

File tree

‎ui/scripts/__tests__/check-doc-links.test.ts‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -668,9 +668,12 @@ describe('the repo it guards', () => {
668668
}
669669

670670
// 25 until objectstack#27145: the SDK pages that carried most of them left
671-
// this workspace, and the monorepo copies link the docs site instead. Two
672-
// when re-measured, so the floor only keeps the loop from going vacuous.
673-
expect(targets.size).toBeGreaterThanOrEqual(1);
671+
// this workspace, and the monorepo copies link the docs site instead. The
672+
// last two went with the vscode-extension package (#27275), so the tree
673+
// holds none today and there is no population floor to keep. What stops
674+
// this from passing over a broken extractor is the `selfRepoPath` unit
675+
// test further down, which feeds it the URL shapes directly; this case
676+
// keeps the gate for the next self-repo URL someone writes.
674677
expect([...targets].filter((target) => !fs.existsSync(path.join(repoRoot, target)))).toEqual([]);
675678
});
676679

0 commit comments

Comments
 (0)