Extension policies #13
Merged
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
Closed
SpyQuel
force-pushed
the
feature/12-evolution-policies
branch
from
3db160f to
e1af92f
Compare
SpyQuel
force-pushed
the
feature/12-evolution-policies
branch
2 times, most recently
from
d046abd to
0c0d97d
Compare
SpyQuel
force-pushed
the
feature/12-evolution-policies
branch
from
0c0d97d to
5fe4486
Compare
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.
With this PR we introduced the basic rules for extending the Data Product Specification and identified a first set of "reserved" fields.
To make the specification more robust, and expose also a way for users to validate their own specifications, we introduced a CUE file that validates the example attached to the specification.