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
Annotating Bar with @ActivityScope means "All instances of Bar should belong to a scope that supports the scope annotation @ActivityScope". All the dependencies of Bar will also be found in such a scope or its parents.
As an example, if we take an app with 2 activities, that owns a dedicated scope.
If both activities (without support of @ActivityScope) will inject Bar() => KTP will complain ? Runtime or compile time ?
If both activities (with support of @ActivityScope) will inject Bar() => KTP will inject bar depending on binding setup by KTP in each activity ?
If both activities (with support of @ActivityScope) => does not mean this is the same scope for both activity, but same type of scope (more or less)
If both activities (with support of @ActivityScope) will inject Bar() => does not mean Bar() has the same instance management in both activity instance (eg singleton), it really depend of each scope bind setup ?
If only a single activity from 2 would have support for the @ActivityScope, this means, Bar should only be injected in this activity, but not in the other activity scope ?
Did I understand it ?
Could someone give more operationnal / industrial use cases about this ?
The text was updated successfully, but these errors were encountered:
Could you maybe rephrase the definition, or the target of the feature, because I do not understand well how it does work and for what purpose it is !
the doc says : https://github.com/stephanenicolas/toothpick/wiki/Scope-Annotations
As an example, if we take an app with 2 activities, that owns a dedicated scope.
Did I understand it ?
Could someone give more operationnal / industrial use cases about this ?
The text was updated successfully, but these errors were encountered: