This repository has been archived by the owner on Oct 10, 2024. It is now read-only.
Fix #860: Nested Type name clashes within same package #879
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #860 , when we are using a class with name both appearing in the inner declaration of current super class, and a individual class in current package, the later one's name would be the simplest form (e.g.
Nest
). However, it should becom.squareup.javapoet.Nest
and theNest
should be the name of inner class.Therefore, an judgement is added in the trim step in
lookupname
. With that, the name of external class in same package would not be trim any longer and will be write as its full name.By the way, in order to test this situation, two other class is added in
test
. They don't look good, but that's the only way I know to get the bug's situation.