Skip to content
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

Closed
sstone1 opened this issue Jun 8, 2022 · 1 comment
Closed

Compare two versions of a model #442

sstone1 opened this issue Jun 8, 2022 · 1 comment
Assignees
Labels
Type: Feature Request 🛍️ New feature or request

Comments

@sstone1
Copy link
Contributor

sstone1 commented Jun 8, 2022

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:

  • Automatically determine the next version number (major vs minor/patch)
  • Automatically reject new minor/patch versions that make breaking changes and warrant a major version

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).

@sstone1 sstone1 added the Type: Feature Request 🛍️ New feature or request label Jun 8, 2022
@sstone1 sstone1 self-assigned this Jun 8, 2022
sstone1 pushed a commit to sstone1/concerto that referenced this issue Aug 5, 2022
sstone1 pushed a commit to sstone1/concerto that referenced this issue Aug 5, 2022
sstone1 pushed a commit that referenced this issue Aug 5, 2022
sstone1 pushed a commit to sstone1/concerto that referenced this issue Aug 5, 2022
sstone1 pushed a commit to sstone1/concerto that referenced this issue Aug 5, 2022
sstone1 pushed a commit to sstone1/concerto that referenced this issue Aug 5, 2022
sstone1 pushed a commit to sstone1/concerto that referenced this issue Aug 5, 2022
sstone1 pushed a commit that referenced this issue Aug 5, 2022
sstone1 pushed a commit that referenced this issue Aug 5, 2022
sstone1 pushed a commit that referenced this issue Aug 5, 2022
@sstone1
Copy link
Contributor Author

sstone1 commented Aug 9, 2022

I think this is done now!

@sstone1 sstone1 closed this as completed Aug 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Request 🛍️ New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant