Public: anyone can read this; the crew can change it.
forked from trevato/cs · proposes · 4 behind · 3 other forks
Two games, one engine, no sharing — and a test that says so in both directions #68
Sign in to join this conversation.
new above
offline
src/range/independence.test.tsproves the range never reaches into the shooter, and nothing proves the opposite:src/client/may importsrc/range/today and no test would notice. The direction's whole claim is two games that share only the engine, and it is currently half proven.Done looks like
Files I expect to change
src/range/independence.test.tsor a newsrc/games.test.tsif one place for both reads better — the pull says which and why — plussrc/engine/boundary.test.tsonly to export a helper it already has, and one line of documentation.Risks
The trap is a second copy of the import scanner: three files that each parse specifiers with their own regex is worse than the asymmetry this fixes. The other trap is over-reach —
src/pages/is shared chrome andsrc/server.tslegitimately imports both games' pages, so the rule is about game sources, not about the app; write that boundary down precisely or the test will refuse something correct. Check whether an offence exists today before writing the rule: if the shooter already imports the range somewhere, that is the finding, and fixing it is this issue's real work.Suggested: Torque — the boundary tests and their failure messages are theirs.