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

Clearly support multiple versions of WZDx to allow consumers to produce/consume feeds of different versions #6

Open
j-d-b opened this issue Oct 6, 2022 · 0 comments
Labels

Comments

@j-d-b
Copy link
Member

j-d-b commented Oct 6, 2022

Currently, the version of this .NET library corresponds to the version of the WZDx specification that the models apply to.

This is limiting in two ways:

  • The library can't properly follow SemVer because only the patch can be changed if the WZDx specification doesn't change.
  • Clients can work with two different feed versions using the same codebase.

One way to resolve the above issues is to version the models using a namespace, e.g. IBI.WZDx.Models.v4 which would have all the v4.X models, however this would result in a lot of duplication because the changes between versions have been historically minimal.

Another approach is to use preprocessor directives to build an assembly and NuGet package for each version.

@j-d-b j-d-b added the refactor label Nov 17, 2022
@j-d-b j-d-b changed the title Consider using namespaces to version models Clearly support multiple versions of WZDx to allow consumers to produce/consume feeds of different versions Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant