Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KSP2: Resolver.getJvmNames doesn't work for inline and internal classes #1640

Closed
ting-yuan opened this issue Dec 4, 2023 · 1 comment · Fixed by #2080
Closed

KSP2: Resolver.getJvmNames doesn't work for inline and internal classes #1640

ting-yuan opened this issue Dec 4, 2023 · 1 comment · Fixed by #2080
Assignees
Labels
AA waiting for upstream fix bug Something isn't working P1 major features or blocking bugs
Milestone

Comments

@ting-yuan
Copy link
Collaborator

No description provided.

@ting-yuan ting-yuan added this to the 2.0 milestone Dec 4, 2023
@ting-yuan ting-yuan added bug Something isn't working P1 major features or blocking bugs labels Apr 24, 2024
@ting-yuan ting-yuan added the AA waiting for upstream fix label May 8, 2024
@ting-yuan
Copy link
Collaborator Author

Missing cases are inline and internal classes

@ting-yuan ting-yuan changed the title KSP2: Resolver.getJvmNames only works for a limited case without complex names KSP2: Resolver.getJvmNames doesn't work for inline and internal classes May 8, 2024
@ting-yuan ting-yuan modified the milestones: 2.0, 2.1 May 20, 2024
@ting-yuan ting-yuan assigned ting-yuan and unassigned neetopia Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AA waiting for upstream fix bug Something isn't working P1 major features or blocking bugs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants