Repository navigation
test: remove the import-boundary scanner - #1374
Conversation
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a Context Mill branch:
Add Results will be posted here when complete. |
Generated-By: PostHog Desktop Task-Id: d14e92bb-6ee1-49b5-8502-39cb80079589
e9f257c to
7b932f2
Compare
johncwaters
left a comment
There was a problem hiding this comment.
Note
Automated review. Not written by a human.
Clean removal of the architecture test, its known-violations ledger, the vitest architecture project and the test:arch script. No code or CI references remain, but four docs and comments still cite the deleted test (listed below, none are in the diff, so they are not inline). Also worth confirming that the compiler-level rules from the description land before or with this merge: the deleted test also covered the shared/tui/cli/programs surface matrix and programs deep imports, which ESLint does not cover.
AGENTS.md:211: still sayspnpm test:archrejects deep@agent/*imports; the script is removed. Drop that mention..eslintrc.cjs:102: the comment says the architecture test applies the same rule to resolved paths; that test is deleted. Update the comment.src/shared/README.md:43: describes the architecture test and linksknown-violations.json, both deleted. Reword or remove.src/agent/index.ts:4: says deeper imports fail lint and the architecture test. Say lint only.
This was a ledger for my own sanity. We no longer need this, up stack there is compiler level rules.