Closed benjaminplee closed 7 years ago
This is effectively a dupe of https://github.com/google/dagger/issues/581 and is because of how the sync works (see https://github.com/google/dagger/issues/581#issuecomment-280064012)
Should be released by the end of the week
@JakeWharton Good catch. My search missed that.
I only knew it existed because I follow all the issues. Took a few searches to find!
On Wed, Apr 12, 2017, 10:14 PM Benjamin Lee notifications@github.com wrote:
@JakeWharton https://github.com/JakeWharton Good catch. My search missed that.
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/google/dagger/issues/694#issuecomment-293757842, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEEEXONF9Cl4Tm4ne5ThM6syautXNjZks5rvYUhgaJpZM4M8KDd .
The dagger website, https://google.github.io/dagger/android.html, mentions a nice convenience method for new the dagger.android features to simply setup for most users but this isn't in the latest 2.10 release. @ronshapiro what is the status of the work with the ContributesAndroidInjector annotation? It looks to be on master only.
I would really like this feature as we have a good set of base architecture using an older dagger2 version setup for our last app which was good at reducing boilerplate for new activity setup, but had some other deficiencies.
Is there a Dagger roadmap for v2.11 (or future) where this is planned or anything I can do to help get this ready for prime time?
Issue #691 makes this unfortunate since quick testing with the current snapshot is missing. Also, FYI, there are some 404s on the Javadocs referenced for that page for version "latest" too.