Docs: Toolkit extensibility #317
Conversation
| - [Field migrations](#Customize field migrations) | ||
| - [Widget migrations](#Customize widget migrations) | ||
| - [Widget property migrations](#Customize widget property migrations) |
There was a problem hiding this comment.
Do these links really work? I am nor sure whether this is the correct format of the section link
https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#section-links
|
|
||
| You can see a sample: [SampleWidgetMigration.cs](./CommunityMigrations/SampleWidgetMigration.cs) | ||
|
|
||
| After implementing the migration, you need to [register the migration](#Register migrations) in the system. |
There was a problem hiding this comment.
Do these link really work? I am not sure whether this is the correct format of the section link but in preview it seems to be broken.
| - [File selector migration](./DefaultMigrations/WidgetFileMigration.cs) | ||
|
|
||
| After implementing the migration, you need to [register the migration](#Register migrations) in the system. |
There was a problem hiding this comment.
Do these link really work? I am not sure whether this is the correct format of the section link but in preview it seems to be broken.
| - implement `MigrateValue` where goal is to return new migrated value derived from `object? sourceValue` | ||
| - finally register in `Migration.Tool.Extensions/ServiceCollectionExtensions.cs` as `Transient` dependency into service collection. For example `services.AddTransient<IFieldMigration, AssetMigration>()` | ||
|
|
||
| ## Custom class mappings for page types |
There was a problem hiding this comment.
IMHO the examples for custom class mappings are helpful as well. It contains real scenario samples based on which we have implemented this extension module. Would it be possible to mention custom class mapping scenarios in the new version? Or at least keep the link to Migration.Tool.Extensions/ClassMappings/ClassMappingSample.cs.
Response to #238 (comment) in #238