Skip to content

refactor(ksp): Use fully qualified provider owner names in precompiled path#206

Merged
harrytmthy merged 1 commit into
mainfrom
refactor/use-fqn-for-provider-classes
Apr 25, 2026
Merged

refactor(ksp): Use fully qualified provider owner names in precompiled path#206
harrytmthy merged 1 commit into
mainfrom
refactor/use-fqn-for-provider-classes

Conversation

@harrytmthy

Copy link
Copy Markdown
Owner

Summary

This PR updates Stitch KSP to preserve fully qualified provider owner names for non-top-level @Provides declarations, 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 Companion calls 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

@harrytmthy harrytmthy added this to the 1.0.0 milestone Apr 25, 2026
@harrytmthy harrytmthy self-assigned this Apr 25, 2026
@harrytmthy harrytmthy added the refactor Internal code design/structure improvement label Apr 25, 2026
@harrytmthy harrytmthy merged commit db8610c into main Apr 25, 2026
1 check passed
@harrytmthy harrytmthy deleted the refactor/use-fqn-for-provider-classes branch April 25, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

refactor Internal code design/structure improvement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use fully qualified provider owner names in Stitch KSP codegen

1 participant