Support ODPS v1.1.0 - #11
Merged
Merged
Conversation
Vendor the ODPS v1.1.0 JSON Schema and make lint pick the bundled schema by the document's apiVersion, since v1.1.0 relaxed required fields (status, port version/contractId) and added new ones (type, context, synonyms, deprecated, customProperties[].vendor, element ids). v1.0.0 and v0.9.0 documents keep validating against the v1.0.0 schema. The init template now emits apiVersion v1.1.0.
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.
Summary
type,context,synonyms,deprecated,customProperties[].vendor, elementids, SBOM metadata;statusand portversion/contractIdare now optional.lintvalidates against the bundled schema for theapiVersionthe document declares, mirroring datacontract-cli #1606:v1.1.0→ v1.1.0 schema,v1.0.0/v0.9.0→ v1.0.0 schema, unknown → newest (which then reports the badapiVersion). Needed because v1.1.0 loosened required fields, so a v1.0.0 document must not pass withoutstatusor with v1.1.0-only fields.Data product is valid against ODPS v1.1.0/Check that data product is valid against ODPS v1.0.0); no version is named for a custom--json-schema.initwritesapiVersion: v1.1.0with a commentedtypestub.dataproduct/schemas/downloadto refresh the vendored schemas, parallel to datacontract-cli.status, v1.1.0 fields rejected under v1.0.0, the version map, and check naming.