Closed realityforge closed 4 years ago
After converting several applications it is unclear whether this is actually required. We have not yet needed it yet if the fragments are managed carefully. Will move it to a later release.
After converting several projects to sting, it was found that this no longer seemed necessary if you crafted fragments carefully. Putting a hold on this change for now.
Further experimentation seems to indicate that this is not really needed and really is just a crutch used in earlier DI systems that did not require the level of proceciseness required by sting
Add mechanisms for overriding bindings already added to object graph. This may be implemented by adding an
override=ENABLE|DISABLE|AUTODETECT
parameter which indicates whether the binding can override existing bindings. Order inincludes
matters in this scenario. This will default toAUTODETECT
which will evaluate toDISABLE
in all scenarios except when the binding is from a descriptor declared as a nested class of the injector. Overrides can either be by id or published types.Once completed this should be added as a pro for Sting when comparing with dagger.