resync v3.0 schema.json from yaml #2684
Closed
Conversation
This file contains 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
darrelmiller
approved these changes
Aug 26, 2021
|
@jdesrosiers Could you just verify that this can be closed and then someone from @OAI/tsc will close. |
|
@OAI/tsc This can be closed. All the needed changes were included in #2718. |
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.
This PR mechanically resync's the v3.0
schema.jsonfrom its yaml counterpart. It picks up the changes from #2673 (scopes) and #2157 (References for headers in encoding objects).The GitHub Action to automate this is still a WIP.
There are a few 'whitespace' changes with respect to empty objects (
{}) but these would have been generated by the Action also, as it too will use the canonical Javascript JSON stringification function.Thanks to @char0n for prompting this.