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.

Sign up for GitHub

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

Jump to bottom

[Domain] Review semantic version validation rules #75

Closed
wwerner opened this issue Oct 29, 2019 · 1 comment · Fixed by #116
Closed

[Domain] Review semantic version validation rules #75

wwerner opened this issue Oct 29, 2019 · 1 comment · Fixed by #116
Assignees
@wwerner

Comments

@wwerner
Copy link
Contributor

wwerner commented Oct 29, 2019

Currently, a schema version of maj.min+1.patch or maj+1.min.patch cannot be created if preceeded by maj.min.patch in status Draft. A version of maj.min.patch+1 can be created.

It is not entirely clear to me what the actual business rules encompassing previousVersion, currentVersion and status should be.
@wwerner
Copy link
Contributor Author

wwerner commented Dec 8, 2019 •
edited
Loading

From @VaughnVernon in #105 (comment):

version backward compatibility check when new version with same major version added.

Disallowed

  • removed attributes
  • renamed attributes
  • type change on attributes
  • reordering of attributes

Allowed

  • Additive only attributes with no name clashes

@wwerner wwerner mentioned this issue Dec 8, 2019
Closed
26 tasks
@wwerner wwerner mentioned this issue Dec 27, 2019
Merged
@wwerner wwerner self-assigned this Feb 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wwerner wwerner

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add semantic version compatibility checks vlingo/xoom-schemata
1 participant
@wwerner