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
We should probably rethink our manifest migration strategy. While we can have all of these options set as optional manifest properties, I'd say that we'll likely want to create a proper migration strategy sooner than later, as it will reduce future work.
Current migration strategy:
Auto-generated code requires us to implement certain, fixed migrators.
Allow developers to declare their own migrators, from whichever version to whichever other version.
A simple search algorithm would then find the appropriate migration path, and could even allow for downgrades if the correct migrator exists.
This ensures any migration can always happen, even when nobody adds a shorter path. Even though this is the longest path, the migrators are inexpensive and it won't be a practical issue.
I think you already had this in mind, but I thought I'd make it explicit just in case.
We should probably rethink our manifest migration strategy. While we can have all of these options set as optional manifest properties, I'd say that we'll likely want to create a proper migration strategy sooner than later, as it will reduce future work.
Current migration strategy:
Auto-generated code requires us to implement certain, fixed migrators.
After update to 0.5.0:
We need to update/create
n+1
migrators if we want full migration support.Proposed migration strategy:
Allow developers to declare their own migrators, from whichever version to whichever other version.
A simple search algorithm would then find the appropriate migration path, and could even allow for downgrades if the correct migrator exists.
After update to 0.5.0:
The text was updated successfully, but these errors were encountered: