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

ksp-codegen: Spring/JPA barfs on accessing private fields #985

Open
1 task done
mkoertgen opened this issue Mar 13, 2025 · 0 comments
Open
1 task done

ksp-codegen: Spring/JPA barfs on accessing private fields #985

mkoertgen opened this issue Mar 13, 2025 · 0 comments

Comments

@mkoertgen
Copy link

Important Notice

Thank you for opening an issue! Please note that, as outlined in the README, I currently only work on feature requests or bug fixes when sponsored. Balancing this project with professional and personal priorities means I have a very limited amount of effort I can divert to this project.

You must put in the work to address this issue, or it won't be addressed.

  • I am willing to put in the work and submit a PR to resolve this issue.

Describe the bug
The ksp-plugin is missing the option "entityAccessors" like the kapt-plugin does, so that the generated QClasses contain "public val". When booting up a spring application, the JPAAnnotationProcessor throws on accessing private final fields.

To Reproduce
Steps to reproduce the behavior:

  1. Have a minimal spring/jpa application
  2. Add ksp-plugin
  3. Try using the Qclasses for any Entity
  4. See error

Expected behavior
...

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant