cabloy-resource-field-update

To update an existing Cabloy backend resource field, you must apply an entity-first workflow that classifies whether the change is a persisted field addition or metadata-only refinement, then coordinate fileVersion decisions and renderer synchronization instead of triggering a full resource rebuild.

Adding a validated enum field to a Cabloy resource requires updating the backend entity first, deciding on a migration strategy for the persisted data, refining the enum metadata, and finally configuring the select renderer to ensure backend and frontend synchronization.

You need to manage fileVersion decisions during a Cabloy resource field update whenever you add persisted fields or alter validation rules, as this determines the appropriate migration strategy and ensures backend metadata changes are safely propagated without breaking existing data structures.

Updating Cabloy resource field validation does not always require custom renderer integration; the workflow supports reusing shared renderers for standard metadata refinements, but custom renderer demonstrations are needed when configuring specific select rendering behaviors for new validated fields.

The best way to verify synchronization after modifying a ZovaRender configuration is to perform targeted verification checks that validate the inferred DTO flows, confirm locale handling, and ensure the shared renderer correctly displays the updated Cabloy resource fields.

You should distinguish between persisted field additions and metadata-only refinements in Cabloy because persisted additions require database migration and fileVersion management, whereas metadata-only refinements like enum adjustments or locale handling bypass heavy migrations and focus directly on renderer synchronization.