Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Allow `@RequestScope` on method declarations #14
Comments
bazel HEAD appears to be incompatible with the version of dagger we were running. This change updates the donuts domain-registry to use the same version of dagger used by the google/domain-registry project (as of today)
When using dagger to inject the current route, it would be useful to reuse that route within the scope of the request so that the router isn't invoked multiple times. According to https://guides.codepath.com/android/Dependency-Injection-with-Dagger-2#scopes dagger module
@Providesmethods will be called repeatedly without caching the result: "Scope annotations cause dagger to hold a single instance of the provided object in a given component. Provider methods that do not have a scope specified will be called to create a new object every time that the given type is injected."In order to cache request scoped objects,
@RequestScopeshould allow METHOD targets so that it can be added to@Providesannotated methods in dagger modules.The text was updated successfully, but these errors were encountered: