feat: chain with independent convert functions #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implementing 2-way conversion was not possible in most cases due to Golang package cycle restrictions. This PR (WiP) moves conversion to functions such that these are able to be defined outside of the packages where the target structs are defined. Take the following example:
..
v1/models
cannot refer tov2/models
AND havev2/models
refer back tov1/models
. This PR allows the custom conversion functions to be defined outside the origin structs, for example:where the functions defined in
v1to2/convert
are able to reference BOTHv1/model
andv2/model
, e.g.:this allows the backwards migrations to also be defined, either in the same or another package, e.g.: