Add DocMigrator to handle deserialization and migrations#170
Add DocMigrator to handle deserialization and migrations#170Timmoth merged 2 commits intoTimmoth:mainfrom
Conversation
Signed-off-by: Stephen Reaves <reaves735@gmail.com>
|
Also, this required some version bumps to get working with docmigrator, so I ran |
|
I would say create a new Deserializer class called Then register it during startup in DI (it's fine to be a singleton and include the yaml (de)serializer builder config) Then then call
on line 135 instead of
The only missing bit now is to determine if a migration is necessary (prior to deserialization), such that we can decide to save a backup copy. (maybe this should be a feature of doc migrator?) Something like: |
Signed-off-by: Stephen Reaves <reaves735@gmail.com>
This is currently a WIP as I'm still not exactly sure how to instantiate the migrator and include the prebuilt deserializer. This is a little out of my dotnet depth so it may take me a bit to figure out, but I'm going to go ahead push here to get some more eyes on it