syncable-entity-builder-and-validation

Syncable entity validation is implemented using non-throwing validators that enforce business rules without mutating data. They run during workspace migration development to check creation, updates, and deletions safely before passing results to the orchestrator.

Building syncable entity migration actions is handled by a builder service integrated with the WorkspaceMigrationBuilderService. It creates structured create, update, and delete actions while using optimistic maps for O(1) lookups.

The orchestrator integrates with syncable entity validators and builders by wiring them together during workspace migrations. It runs validators to enforce constraints, then emits structured creation, update, and deletion actions generated by the builder.

Optimistic maps are needed for syncable entity migration validation to achieve O(1) lookups when checking related constraints. They allow validators to efficiently verify creation, updates, and deletions against existing entities during workspace migration development.

Yes, non-throwing validators check workspace migration constraints without mutating data or throwing exceptions. They enforce business rules for syncable entities and return validation results directly to the migration orchestrator for processing.

The WorkspaceMigrationBuilderService is limited to Twenty workspace migrations and requires strict integration with the orchestrator. Validators must be non-throwing and use optimistic maps for O(1) lookups, ensuring constraints are enforced without mutating data.