Add a JSON schema for Content Patcher include files - #1035
Open
eth0net wants to merge 1 commit into
Open
Conversation
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
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.
There's currently no schema for
Includefiles, even though the format is a subset of the main content file —Changesalone, withoutFormat.content-patcher.jsoncan't stand in for the same reason: it requiresFormat.This adds
content-patcher-include.json. It$refscontent-patcher.json#/properties/Changesrather than duplicating it, so it shouldn't need maintaining alongside the main schema — I'd been using a hand-written copy of that subschema locally, and it had fallen out of date within a few months.Thanks for publishing these — they've saved me a lot of time working on content packs. Glad to rename it, adjust the wording, or close this if you'd rather not carry another file.