You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, thanks for the continuous work on Typhoon, it's shaping up great!
I've been trying to use -[TyphoonComponentFactory injectProperties:] to inject properties marked as auto-wired into an existing instance that was manually initialized using some data that's only available when the instance in question is required (note: I've tried TyphoonFactoryProvider but I'll reserve that for a StackOverflow question). I found out though that -injectProperties: only checks the TyphoonComponentFactory's registry for existing definitions and doesn't resolve auto-wired properties.
I would expect not to be forced to register a class explicitly in the assembly for it to work with -injectProperties: (like is the case with -componentForType:). Is there some logic behind this behaviour that I'm not getting?
In essence, I would expect all objects that are returned or processed by Typhoon in some way (including -injectProperties:) to always return a fully-injected instance, however dependencies are defined.
The text was updated successfully, but these errors were encountered:
Hi there, thanks for the continuous work on Typhoon, it's shaping up great!
I've been trying to use
-[TyphoonComponentFactory injectProperties:]
to inject properties marked as auto-wired into an existing instance that was manually initialized using some data that's only available when the instance in question is required (note: I've triedTyphoonFactoryProvider
but I'll reserve that for a StackOverflow question). I found out though that-injectProperties:
only checks theTyphoonComponentFactory
's registry for existing definitions and doesn't resolve auto-wired properties.I would expect not to be forced to register a class explicitly in the assembly for it to work with
-injectProperties:
(like is the case with-componentForType:
). Is there some logic behind this behaviour that I'm not getting?In essence, I would expect all objects that are returned or processed by Typhoon in some way (including
-injectProperties:
) to always return a fully-injected instance, however dependencies are defined.The text was updated successfully, but these errors were encountered: