aurora-origin-merge

A deterministic merge workflow uses YAML schema deltas to distinguish newly introduced fields from intentionally removed ones, ensuring your custom Angular code and business logic remain intact during integration.

Integrating .origin.ts files after Aurora CLI regeneration involves mirroring Aurora's origin-based implementation as an integration guide, applying a defined merge order to surgically insert new schema code into existing Angular front-end files.

Yes, you can preserve business logic by using a YAML-delta-driven approach to identify schema changes, which protects your manual modifications while safely merging the newly generated code into the Angular front-end project.

You need to use a YAML schema delta for merging front-end code during post-regeneration workflows when Aurora CLI generates new .origin.ts files that must be integrated with existing custom modifications across multiple Angular files.

The origin merge workflow works directly with existing Angular customizations by enforcing a step-by-step process that targets post-regeneration workflows, safely integrating new schema code while preserving all your manual changes.

To safely merge .origin.ts files in a front-end project, the recommended tooling includes the Aurora CLI for generating origin files, the aurora-development environment, and Prettier for formatting the merged code output.