Trapline: Checkpoints, Hazards and Lives Kit
- Author
- claude-code @ auraAgent
- Opened
- Nov 3, 2026
- From
- contrib-01m6hvzx
- Into
- main
- Merge
- Can be merged
barsKit.testSuite and matchflow.testSuite read their own files at hard-coded paths, /zero/source/barsKit.package/... and /zero/source/MatchFlow.package/.... When Trapline brings them, they live under /source/deps/<world>/, so in a world that installs Trapline (or platformsKit) 5 barsKit tests and 10 MatchFlow tests fail (version, README, guide, source checks), and one barsKit test ("does not run the gallery's sample when its script loads in edit mode", line 1038) WRITES /zero/source/barsKit.package/Showcase.component/init.luau, leaving a stray placeholder component at the top of /source whose [[describe]] README then blocks zm push. Fix: each suite resolves its root once, local ROOT = asset.resolve("<kit>", "package").path, and every hard-coded path becomes ROOT .. "/...". Nothing else changes. Checked in Platform Playground (both kits under /source/deps/ via Trapline 1.5.2): barsKit + matchflow 151/151 (was 136/151), and no file appears outside the package. In each kit's own world ROOT is /zero/source/<kit>.package, so the tests read exactly what they read before. These two copies belong to barsKit's and MatchFlow's own worlds; please send them on there.
Source world: ed62a6a5-b580-47d2-9d65-3eb60ebe0b01 Contributed paths:
- MatchFlow.package/matchflow.testSuite/init.luau
- barsKit.package/barsKit.testSuite/init.luau
- MatchFlow.package
- MatchFlow.package/matchflow.testSuite
- barsKit.package
- barsKit.package/barsKit.testSuite
6 files changed
Checks
No checks have been posted.
Reviews
No reviews yet.
Conversation
No comments yet.
Sign in to comment or review.