Inner-Class Component Generated Code Naming
See original GitHub issuepublic class Foo {
@Component
public class Bar {}
}
produces Dagger_Foo$Bar
. AutoValue produces names in the form Dagger_Foo_Bar
which seems much more desirable.
Issue Analytics
- State:
- Created 9 years ago
- Comments:17
Top Results From Across the Web
Inner Classes - Learning Java [Book] - O'Reilly
Inner classes rely on code generation; they are a feature of the Java language, but not of the Java virtual machine. As a...
Read more >Java inner class and static nested class - Stack Overflow
A nested class is a class which is contained in another class at the source code level. It is static if you declare...
Read more >Javanotes 9, Section 5.8 -- Nested Classes
From outside the containing class, however, an inner class has to be referred to using a name of the form variableName.
Read more >Inner Classes Specification - Java Community Process
The code of an inner class can use simple names from enclosing scopes, including both class and instance members of enclosing classes, and...
Read more >Nested Classes - Learning the Java Language
It can lead to more readable and maintainable code: Nesting small classes within top-level classes places the code closer to where it is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Dagger 2.0 has been released, and the names are, for @Component Foo you get DaggerFoo, and for @Component Bar.Blah (nested) you get DaggerBar_Blah as the implementation types for components.
On Mon, 13 Apr 2015 at 10:41 TJ (Thomas J.) Biddle notifications@github.com wrote:
Fixed in #150