[Refactor]: Move ProvisionMethods#create()
/InjectionSiteMethods#create()
into the generator that uses it.
#4516
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.
[Refactor]: Move
ProvisionMethods#create()
/InjectionSiteMethods#create()
into the generator that uses it.Note: this CL shouldn't cause any changes to the generated code.
FactoryGenerator
is the only class that usesProvisionMethods#create()
, andMembersInjectorGenerator
is the only class that usesInjectionSiteMethods#create()
. Thus, I'm moving these methods into these classes for better encapsulation. This will also make the XPoet migration easier since I plan to migrateFactoryGenerator
andMembersInjectorGenerator
separately.Note that these methods were sharing some logic that now needs to be duplicated, but IMO this creates more readable code since we're no longer entangling the two use cases. For example, now that
ProvisionMethods
andInjectionSiteMethods
define their own versions ofmethodProxy()
method, we no longer need the multiple enums (i.e.InstanceCastPolicy
andCheckNotNullPolicy
) as input to these methods.RELNOTES=N/A