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
Following my last blog and the code samples in its summary.... I am wondering if an option for the Apex Injector to optionally require a binding if the binding reference (the class) is in-fact also the implementation. This would support simple cases where the developer just wants to use the Injector to add injection for a one off type thats not subclassed., but is a dependency they want to mock.
The text was updated successfully, but these errors were encountered:
Following my last blog and the code samples in its summary.... I am wondering if an option for the Apex Injector to optionally require a binding if the binding reference (the class) is in-fact also the implementation. This would support simple cases where the developer just wants to use the Injector to add injection for a one off type thats not subclassed., but is a dependency they want to mock.
The text was updated successfully, but these errors were encountered: