Repository navigation
Conversation
…test.ts under max-lines #4604 added one R11 export entry to a file that main had already grown to 1000 lines, so main's oxlint max-lines check fails at 1001. The removed comment repeated the in-memory fixture note a few tests above. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Size Report
Startup median (7 runs, lower is better):
|
Apex Sentinel · ✅ ApproveNo open findings. 1 finding below 💬 Talking to SentinelIn a finding's thread, reply with:
On this conversation, comment |
|
This PR is ready at 23c89e1. The change only deletes a comment in a test file, so it cannot affect any runtime route, and all 20 checks pass. Not blocking, and you can take or leave it: the file now sits exactly at the 1000-line cap, so the next added line will break lint again, and splitting it by test group when next touched would fix that (the deleted comment at scripts/layering/package-boundaries.test.ts:275 explained the in-memory fixture for the src/utils literal). |
Summary
Main's CI fails at
fce2fa6247on oxlint:scripts/layering/package-boundaries.test.ts:1001:4: File has too many lines (1001). #4604 added one R11 export entry (@agent-device/capture-kit/capture-fact-grace) while main had already grown the file to exactly 1000 lines, so each change passed on its own and the merge broke the cap.This removes one comment that repeated the in-memory fixture note a few tests above (
// These src/utils paths are in-memory arbitrary parser fixtures…). No gate reads that comment; the retired-paths policy checks tracked files, not string literals. The file is back to 1000 lines.Validation
wc -lreports 1000;max-linesinoxlint.config.tscounts comment lines (noskipComments).🤖 Generated with Claude Code
Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.