Overview

The collection model holds a validation prop populated from collectionInfo when the model is fetched. The schema-validation plugin fetches its own copy of the rules and never updates the model after a successful save, so the model goes stale once a user edits validation in the Validation tab and navigates away.

This matters more now that the mock data generator reads validation from the collection model instead of issuing its own fetch (CLOUDP-449267), so stale model data would feed outdated rules into script generation.

Update the collection model from the validation tab after a successful save — either set the new validation on the model or do a forced fetch with fetchInfo — so all consumers read current rules from the model instead of duplicating fetches.

Acceptance Criteria

• Saving validation rules in the Validation tab updates the collection model.
• A consumer reading validation from the collection model after an edit sees the saved rules without refetching.
• No extra listCollections calls are added outside the model update.

Related

• CLOUDP-449267 — mock data generator now reads validation from the collection model
• CLOUDP-443499 — experiment-to-flag cleanup that surfaced the dependency