refactor(ksp): Use fully qualified provider owner names in precompiled path#206
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR updates Stitch KSP to preserve fully qualified provider owner names for non-top-level
@Providesdeclarations, fixing code generation for companion objects and nested provider owners.Implementation Details
Provider owner information is now treated consistently across scanning and code generation. Top-level providers still use package plus function name, while object-backed and class-backed providers now use their fully qualified owner path directly. This fixes previously broken generated references such as unresolved
Companioncalls and also ensures provider-backed fields are generated with the correct owner type for nested declarations. The supported provider model remains intentionally limited to top-level functions, objects, and instantiable classes.Closes #205