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
TyphoonBlockComponentFactory has a resolveInstanceMethod that allow using the Assembly interface to retrieve components. . . this is more prefereable than resolving by string.
Perhaps it could be enhanced to trampoline non component matching methods back to the assembly class?
This would allow custom factory methods. For example:
[assembly photoClientForId:facebook caching:YES];
The text was updated successfully, but these errors were encountered:
Interesting! I spent some time on Thursday working on 'parameterized providers', which would allow something similar. Namely, passing in definitions or even objects at runtime into other definition returning methods on the assembly. See #47 and the experimental branch I just pushed.
TyphoonBlockComponentFactory has a resolveInstanceMethod that allow using the Assembly interface to retrieve components. . . this is more prefereable than resolving by string.
Perhaps it could be enhanced to trampoline non component matching methods back to the assembly class?
This would allow custom factory methods. For example:
[assembly photoClientForId:facebook caching:YES];
The text was updated successfully, but these errors were encountered: