I have couple of questions regarding app and schema version management related to SwiftData migration.
For instance, it's common for the schema to change from V1 to V2 when updating an app from V1 to V2 and V3.
This process seems reasonable to me.
here's Moreover, if the versions go up to V10, does this mean I need to separate and organize stages for all migration codes, such as from V1 to V2, V2 to V3, up to V10, MigrationStages and Models for such exception handling?
It was too wordy, here are my summary questions.
1. Can I limit to specific versions in my workspace?(e.g V1->2->3->1->2 .. so on)
2. if its not possible, For extensive versioning up to V10, should migration codes be organized for every incremental update for handling exceptions?
3. If I need to permanently record every stages and model, what improvements could be made to this structure?, can I get some useful tips?
