extend-map-config

To safely evolve a Zod schema without breaking existing configs, apply a schema-first approach by adding fields in config.ts, deriving types, and setting defaults to maintain backwards compatibility across the workflow.

The correct order to propagate MapConfig schema changes starts with the schema, then moves through tests, the Zustand store, URL state, and finally the admin editors to ensure end-to-end consistency.

To update the Zustand store and URL state after changing a TypeScript schema, hydrate the store with the new defaults and reflect the schema modifications in the URL state to maintain synchronization.

Yes, you can add new fields to a config schema and keep old configs valid by defining appropriate default values during the schema-first migration, ensuring existing configurations remain functional.

Admin editors break after updating the MapConfig schema when changes are not fully propagated end-to-end, requiring updates to tests, store hydration, and UI components to restore functionality.

Yes, this schema migration approach works without external dependencies, relying solely on the existing Zod-based schemas, TypeScript types, and the prescribed workflow to guide safe end-to-end propagation.