Yes, @kharrison I noticed that when trying this in beta 5. I did almost the same as you, just copied the name of the migration inside the string. This is just a blind guess because I see absolutely no docs about this. I then tried a couple of different initializers with no success BUT... I think I got lightweight migrations working.
Amazingly, they seem to work if you just modify the @Model class directly and re-run the app. You don't have to specify a migration or anything. Just provide default values for new attributes and it works!!!
If you don't provide default values, the app will fail to start with an error that the migration failed.
diegooo
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Just posted a Feedback for this (FB12759179)
I just checked with the latest version of Xcode (Beta 5) and this issue is still present.