You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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:
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.
The text was updated successfully, but these errors were encountered: