Michael Long
Michael Long
You don't show AppSettings but indicated right off the bat that it's a struct, so I'm not clear on how it's supposed to trigger an update since a struct can't...
I kind of mentioned this, but the InjectedObject wrapper as implemented above will call the Factory to get an instance of the object every single time the view is evaluated....
I had a version of it. See the example just before Mocking and Testing. "Finally, note that it's possible to bypass the property wrapper and talk to the factory yourself...
Updated README with section on SwiftUI.
I'll need to look at the pros and cons of doing this...
Wow. Yeah, I've the word "service" in various contexts over the years. The oldest use really came from Resolver, which borrowed the name from Swinject. From the DI perspective, every...
I haven't used Swift Concurrency enough to be aware of all of the pain points. Most of what I've done thus far is marking certain functions MainActor as opposed to...
Insofar as I can tell there's one use case that's problematic and that's when an entire class is marked with MainActor. ```swift extension Container { static var myActor = Factory...
> I believe is a good usecase, we for example use that quite a lot to create our ViewModels which indeed need to be marked as `@MainActor` especially if being...
Rewatched a few WWDC videos and realized that you can do the following... ```swift extension Container { static var mainActorTest2 = Factory { MainActorTest() } } @MainActor class MainActorTest {...