Sails IDL Client

Goal

Keep Sails builders on the typed pipeline for IDL generation, Rust client generation, and integration wiring.

If a released contract evolves or a new deployed contract version is introduced, keep the generated-client path compatible with the approved cutover plan instead of assuming one regenerated client can replace all consumers immediately.

Default JS Or TS Path

• Treat the program .idl as the source of truth for the interface.
• Generate the normal client with sails-js or sails-js-cli so the workspace gets lib.ts and typed program or service classes instead of hand-written payload code.
• Pair the generated client with GearApi from @gear-js/api for node connectivity.
• Use parseIdl from the sails-js and sails-js-parser path only when you explicitly need dynamic runtime control rather than pre-generated files.

Build Script Path