feat: update schema specification with JSON schema validation #122
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.
Description
A new schema for API specifications, along with JSON schema files that can
be used to validate specification, and runtime conversion of new schema
to the old one to avoid large changes across our codegen templates.
Motivation and Context
Existing specification had some edge cases that made writing codegen more complicated:
New schema solves those and some other issues, and removes codegen-level data (like NameVariants) that will be implemented in the Sdk and Terraform marshallers.
How Has This Been Tested?
Screenshots (if appropriate)
Types of changes