-
-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compare two versions of a model #442
Labels
Type: Feature Request 🛍️
New feature or request
Comments
sstone1
pushed a commit
to sstone1/concerto
that referenced
this issue
Aug 5, 2022
Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
to sstone1/concerto
that referenced
this issue
Aug 5, 2022
Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
that referenced
this issue
Aug 5, 2022
Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
to sstone1/concerto
that referenced
this issue
Aug 5, 2022
…roject#442) Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
to sstone1/concerto
that referenced
this issue
Aug 5, 2022
Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
to sstone1/concerto
that referenced
this issue
Aug 5, 2022
…accordproject#442) Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
to sstone1/concerto
that referenced
this issue
Aug 5, 2022
…ibutes to accordproject#442) Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
that referenced
this issue
Aug 5, 2022
Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
that referenced
this issue
Aug 5, 2022
Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
that referenced
this issue
Aug 5, 2022
…#442) Signed-off-by: Simon Stone <[email protected]>
sstone1
pushed a commit
that referenced
this issue
Aug 5, 2022
…ibutes to #442) Signed-off-by: Simon Stone <[email protected]>
I think this is done now! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request 🛍️
Provide an API that can be used to compare two versions of a model, and determine if those versions are compatible or not.
Use Case
When we have model versioning (#426), then we need to be able to determine if a new version of a model is compatible or not with the previous version of that model. This will allow users to:
Possible Solution
Compare two metamodel structures, looking for breaking changes vs compatible changes.
Context
Without this feature, we cannot determine and trust whether a new minor/patch version of a model is indeed compatible with an existing version of that model.
Detailed Description
The implementation should be clear as to what constitutes a breaking change vs a compatible change. It may be helpful to provide a consumable list of the changes (field A added to type X, field B renamed in type Y, field C made mandatory in type Z).
The text was updated successfully, but these errors were encountered: