If it was standalone feature, which worked from just extension it would have been great, but these coding key hoops make it useless and error prone. What if I need to add or delete field while developing? Change field type? But I leaned where these stored values are, which is a plus. Also not forget to add privacy manifest for them.
Hi Stewart, great video. Have been struggling with AppStorage and custrom types for a while. Thanks! But, what if a don't want to use @AppStorage? How do I work with this using the UserDefaults inside my ViewModel, for example? I tried something like 'UserDefaults.standard.set(self.performanceStats, forKey: "performanceStats")', where performanceStats is Codable and RawPresesentable, but I get a runtime error: "Attempt to insert non-property list object PerformanceStats for key performanceStats". Suggestions?
Excellent… thank you Stewart 🔥✨💯
Nice. Enabled notification so i don't miss anything
Incredible and very useful video! Thanks a lot! Carry on!
Thanks so much for this good lecture!
You're very welcome!
If it was standalone feature, which worked from just extension it would have been great, but these coding key hoops make it useless and error prone. What if I need to add or delete field while developing? Change field type? But I leaned where these stored values are, which is a plus. Also not forget to add privacy manifest for them.
Hi Stewart, great video. Have been struggling with AppStorage and custrom types for a while. Thanks!
But, what if a don't want to use @AppStorage? How do I work with this using the UserDefaults inside my ViewModel, for example? I tried something like 'UserDefaults.standard.set(self.performanceStats, forKey: "performanceStats")', where performanceStats is Codable and RawPresesentable, but I get a runtime error: "Attempt to insert non-property list object PerformanceStats for key performanceStats". Suggestions?
Great vidéo!