nautilus-codegen

nautilus-codegen turns a validated SchemaIr into generated clients.

It is used both by the standalone nautilus-codegen binary and by the main nautilus generate command.

Supported generator providers

Provider	Output	Install behavior
`nautilus-client-rs`	Rust model files, delegates, runtime helpers	`install = true` adds the output directory to the nearest Cargo workspace; `--standalone` also emits a generated `Cargo.toml`
`nautilus-client-py`	Python package with generated models and runtime files	Default workflow: import the generated `output` package directly. `install = true` copies the same generated files into Python `site-packages/nautilus`; it is a local install convenience, not a PyPI publish step
`nautilus-client-js`	JavaScript runtime plus TypeScript declaration files	Default workflow: import from the generated `output` directory. `install = true` copies the same generated files into the nearest `node_modules/nautilus`; it is a local install convenience, not an npm publish step

The provider string in the schema selects which generator runs. The runtime package/module name comes from the generated output location, or from the local install target above when install = true.

Public entry points

Symbol	Purpose
`resolve_schema_path`	Auto-detects the first `.nautilus` file in the current directory unless one is passed explicitly
`generate_command`	Read -> parse -> validate -> generate -> write
`validate_command`	Read -> parse -> validate without writing output
`GenerateOptions`	Controls install, verbosity, and Rust standalone generation

Current target notes

The generator target is chosen entirely from the schema's generator block.
Python supports interface = "sync" and interface = "async".
recursive_type_depth is currently validated only for the Python target.
Rust generation can still emit bare sources for embedding into an existing workspace instead of forcing a standalone crate.
JS generation writes both runtime files and .d.ts declarations so the generated package works in plain JS and TS projects.
The checked-in examples show the intended consumption pattern today: JS imports from ./generated/..., Python imports from the generated output package on sys.path, and install = true is optional.

Template layout

Area	Location
Rust templates	`templates/rust/`
Python templates	`templates/python/`
JS / TS templates	`templates/js/`
Writers	`src/writer.rs`
Rust generator context	`src/generator.rs`
Python generator context	`src/python/`
JS generator context	`src/js/`

Testing

cargo test -p nautilus-orm-codegen