0.3.0
-
Breaking
Navigator
has now been removed along with thebind
andprepare*
methods. It wasn't going to be scalable in a multi module setting where there was potential of clashes. You should instead usenew YourActivityBuilder().addWhatever().start()
to start your activity. If you're binding, you can use several different options. Consult the updated readme. See #68 for all details.- Changes with how you bind your variables when Activity/Fragment is created. Similar to the above point, it wasn't going to be scalable to have a single point of entry without using reflection. Consult the readme for updated methods. See #68
-
New
- Kotlin extensions for binding. Navigator now generates extensions on your binding targets so you can simply call
bind()
from your Kotlin Activity/Fragment. You can also use the generated extension in Java by callingYourActivityNavigator.bind(this)
whereYourActivityNavigator
is the generated extension. Consult readme for more. - Navigator now publicly makes available the keys that are used for binding. If you haven't given the key for an
@Extra
, Navigator now exposes the key as a public static field in case you want to do some custom binding with it. The fields are prefaced withEXTRA_*
See #65
- Kotlin extensions for binding. Navigator now generates extensions on your binding targets so you can simply call