Scoper - Lightweight Dagger 2 Component Management
Quick Start
Setup will depend on how you want to build your scopes. The following instructions will assume you have scopes as follows:
Application Scope->Activity Scope->View scope...
Each subsequent scope is a subscope built on top of the previous scope.
Create an Application subclass. In it you will initialize the Application Scope's component.
public class MyApplication extends Application {
public static final String SCOPE_TAG = "application_scope";
@Override public void onCreate() {
super.onCreate();
Scoper.cacheComponent(SCOPE_TAG, DaggerApplicationComponent.builder()
.applicationModule(new ApplicationModule(this))
.build());
}
}
Next, in each Activity, you should override the attachBaseContext(Context newBase) method and return an instance of ScoperContext as shown. Doing this in a base Activity class can simplify the process. The Activity should also implement the Scoped interface. This has you supply a scope name that will be used to map the component in the cache. The Type Parameter for the Scoped interface is the component class for that scope.
public abstract class BaseActivity<T> extends AppCompatActivity implements Scoped<T> {
protected T component;
@Override protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
component = Scoper.createComponent(this, initComponent());
}
@Override protected void attachBaseContext(Context newBase) {
super.attachBaseContext(new ScoperContext(newBase, getScopeName()));
}
@Override public String getScopeName() {
return getClass().getName();
}
protected abstract T initComponent();
@Override protected void onDestroy() {
super.onDestroy();
if (isFinishing()) {
Scoper.destroyScope(this);
}
}
}
final class MainActivity extends BaseActivity<MainComponent> {
@Override protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
component.inject(this);
}
@Override protected MainComponent initComponent() {
return Scoper.<ApplicationComponent>withParent(MyApplication.SCOPE_TAG)
.createChild(this, appComponent -> appComponent.plus(new MainModule()));
}
}
This setup should be the same whether you use Fragments/Plain Views/Conductor/etc. for the building blocks of your UI.
How you do the next level of scopes will vary depending on your choice of UI management. Demos are provided to show possible solutions (more on the way).
**Note: In the above example we are using the overloaded method for Scoper#withParent that takes in a String for the tag. Normally, you would want to use the overloaded method that takes a Context (ideally all of your downstream Contexts are ScoperContext instances). Overriding #attachBaseContext in an Application subclass can break some libraries, though, so in the case of getting a reference to the Application component, it is recommended to get it via its scope tag.
This is just one potential way to set up the boilerplate for scoping your components. Scoper has methods like cacheComponent(String scopeName), getComponentForTag(String scopeName), destroyScope(String scopeName) that allow you to manually manage your components without having to implement the Scoped interface or use ScoperContext.
Caching Behavior
The default behavior is to cache components across config changes. This means that each time your class calls createComponent(context, component), if there is an existing component for that scope, the existing instance will be returned rather than the provided new instance.
This behavior can be overridden by calling Scoper.replaceExisting(true).
Setup
Add to your Gradle dependencies (Check badge at top for version information):
buildscript {
repositories {
jcenter()
}
}
dependencies {
compile 'com.brandongogetap:scoper:x.y.z'
}
License
Copyright 2016 Brandon Gogetap Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.