-
-
Notifications
You must be signed in to change notification settings - Fork 1
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 migration in anticipation of Kotlin 2.x #34
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Currently on hold, till I get more time |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Issue Guidelines
Before opening a new issue, please take a moment to review our community guidelines to make the contribution process easy and effective for everyone involved.
You may find an answer in already closed issues:
https://github.com/AniTrend/retrofit-graphql/issues?q=is%3Aissue+is%3Aclosed
Feature Information
Though there isn't any real threat of immediate deprecation or
kapt
inv1.8.0
, in line with the deprecations and removals of features inv1.8.0
of Kotlin, we know that kapt has entered maintenance mode. This is a great opportunity to release a major version of this library as a stable update along with the new version of KotlinSolution Information
See documentation for getting started with KSP: https://kotlinlang.org/docs/ksp-overview.html
Additional context
We won't be changing any of the existing
kotlin-poet
implementations but rather just the annotation processing phaseThe text was updated successfully, but these errors were encountered: