Skip to content
Aurora Catalyst

Rename load to generate

Auto-generated from the source archive. Do not edit by hand — rerun catalyst-changelog-sync instead.

What changed

Section titled “What changed”
  • BREAKING — catalyst load <scope> module is removed. The canonical invocation is now catalyst generate <scope> module --name=<bounded-context>/<module>. There is no alias, no deprecation warning, no shim; running catalyst load … returns oclif’s “command not found” error.
  • The generator-emitted guidance string in front.handler.ts — the cross-aggregate hint for grid-elements-manager widgets pointing at a target without front.embedSupport: true — now references aurora generate.
  • docs/load.md is deleted; docs/generate.md replaces it (regenerated by pnpm prepack). A new spec module-generation-cli codifies the canonical verb and the <bounded-context>/<module> argument grammar.

Why it matters

Section titled “Why it matters”

load described an internal step (reading the YAML schema into memory) instead of what the user actually wants — producing or regenerating code. The new verb aligns with industry conventions (ng generate, nest generate, rails generate) and with the existing spec names (frontend-module-generator, sequelize-repository-generator). Aurora’s codegen is idempotent by design: preservation regions, lockfile-aware overwrites, and the .origin review loop all assume you re-run the command as the YAML schema evolves, and generate makes that contract obvious from the command line alone. Migration is a one-line sed -i 's/catalyst load/catalyst generate/g' over your scripts and docs. Next release bumps the major version (1.0.0 → 2.0.0).

View original proposal