[claude]

Requested by Sebastian Konowrocki · Slack thread

Before / After

The @leancodepl/cyberware-contract-generator-dart package had no tests. It now has 25 tests across three files covering:

• config.spec.ts — the Zod config schema: accepts a valid { schema, outputDir }, rejects a missing/non-string outputDir, strips unknown keys, and throws on .parse of an invalid config.
• loadConfig.spec.ts — resolveOutputDir (absolute paths returned unchanged, relative and parent-relative paths resolved against the config dir) and loadConfig (loads an explicit config path, preserves absolute outputDir, throws on a missing config file, throws on schema-validation failure).
• generate.spec.ts — the end-to-end Dart generation: writes exactly the three expected files (contract.dart, types.dart, connect_to_host.dart), creates the output dir when missing, reuses an existing one, prints the generation message, and asserts the real rendered Dart output — params extension types with pascal-cased section prefixes, Result typedefs (String vs void), RemoteParams getters, the abstract RemoteMethodsBase signatures, promiseValue/toJS wiring for value-returning remote methods, the JSHostMethods external methods, the connectToHost helper, the do-not-edit banner, and the "not a valid contract root" error path.

How

Tests build real contract schemas with mkZodContractSchema/methodDef from @leancodepl/cyberware-contract, generate into temp dirs, and assert the actual generated Dart source.

---

Generated by Claude Code