feat: full-fidelity Edit JSON Schema; deprecate text and soundtrack - #126
Merged
Conversation
…point html/title at rich-text
|
🎉 This PR is included in version 1.15.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
dist/json-schema/now ships a single full-fidelityedit.json(draft 2020-12, self-contained $defs): optionality preserved, complete enums, every asset type,deprecatedflags, descriptions converted from HTML to plain text. Replaces the previous strict-mode artefacts (blueprint, template, detailers, per-schema files), which no longer have a consumer. The/jsonsubpath now exports onlyedit.TextAssetandSoundtrack(includingtimeline.soundtrack) markeddeprecated: true— still accepted, no behaviour change.HtmlAsset/TitleAssetdeprecation notices now point atRichTextAsset.Conversion notes
OAS 3.0 → JSON Schema handled explicitly:
nullable,example→examples,discriminatorstripped (branches discriminate viatypeenums), OAS numericformats dropped, union-leveladditionalProperties: falsedropped (in pure JSON Schema it bans all properties).How to verify
pnpm build && pnpm test:smoke— smoke suite now compilesedit.jsonunderAjv2020({strict: true})and runs behavioural cases (valid edits pass; unknown properties, bad enum values, missing output rejected; deprecated types still accepted). 61/61 passing.