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
The original release (v0.1.x) of ApodiniMigrator included support for migration guide providers to annotate addition, removal and idChange (identifier renames) with so called ProviderSupport objects. Those could be used to resolve uncaught type renames or wrongly classified type renames.
With the rewrite happening in v0.2.0, the feature wasn't reimplemented, as of now. This issue tracks reimplementing this feature.
Solution
As the newly introduced change model enforces the structure of a specific change, one can reimplement this feature with distinct typed versions for addition, removal and idChange cases of the Change enum. Therefore, this can be implemented for any change element.
Additionally, one need to implement a resolving step (ideally in the DocumentComparator) which actually interprets the provided renaming hints, such that a Migrator won't need to manually do that.
Problem
The original release (v0.1.x) of
ApodiniMigrator
included support for migration guide providers to annotateaddition
,removal
andidChange
(identifier renames) with so calledProviderSupport
objects. Those could be used to resolve uncaught type renames or wrongly classified type renames.With the rewrite happening in v0.2.0, the feature wasn't reimplemented, as of now. This issue tracks reimplementing this feature.
Solution
As the newly introduced change model enforces the structure of a specific change, one can reimplement this feature with distinct typed versions for
addition
,removal
andidChange
cases of theChange
enum. Therefore, this can be implemented for any change element.Additionally, one need to implement a resolving step (ideally in the
DocumentComparator
) which actually interprets the provided renaming hints, such that a Migrator won't need to manually do that.Additional context
#6
Code of Conduct
The text was updated successfully, but these errors were encountered: