Replies: 1 comment 2 replies
-
|
Best to be positive. |
Beta Was this translation helpful? Give feedback.
-
|
Same question here. What If I really need to observe a property change so it can't be ObservationIgnored? If so we would be synthesizing two properties with the same name (_ myService). I can of course match something similar using a published property on myService, but I'd rather not to mix 2 diff observation patterns . |
Beta Was this translation helpful? Give feedback.
-
|
The property wrappers are a convenience, nothing more. You're perfectly free to pass a container in the initializer or just access the desired factory directly via Container.shared. One should also remember The Law of Demeter, which says that a given object should only talk to its immediate collaborators, not to strangers' strangers. If you're observing through a lot of chains like myService.x.y.z, you're probably reaching across too many boundaries, and that signals a structural problem in your code. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There is an example in Readme
Do I really need to add @ObservationIgnored when myService is private? I think it is ignored automatically
Beta Was this translation helpful? Give feedback.
All reactions