The supplied read-only Help source documents this task. Confirm file-size suitability, load behavior, background validation, result refresh timing, and the current Windows controls before standardizing this workflow.
Prepare a focused large-schema change
- Work from a version-controlled schema and preserve a representative JSON instance for validation.
- Open only the files and referenced resources needed for the change.
- Find the relevant branch, definition, or reference before editing broad sections of the schema.
- Keep a small expected-valid and expected-invalid JSON sample ready for the affected rule.
Use background feedback as a review aid
The retained Help evidence shows background validation while a schema is edited. Use current findings to locate likely structural mistakes, such as a reference that no longer resolves or a required property without a matching definition. Do not assume the historical refresh timing, resource limits, or finding severity still applies to the current release.
Validate the intended contract after the change
Run the current schema-analysis and validation workflow after each meaningful change. Inspect both the JSON data location and the schema location behind a failing result. Retest the expected-valid sample as well as the expected-invalid sample so a correction does not quietly broaden or remove the intended constraint.