-
Notifications
You must be signed in to change notification settings - Fork 450
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
1.1.5 to 1.2.1 Migration - arrow.resilience.Schedule causes 'bad class file' error in Dagger KSP #3325
Comments
Hi! Sorry for taking such a long time. This kind of problems usually happen when the names of type parameters do not coincide with the ones in the class. So I would like to ask some further question: how is the |
This is one of two declaration variants in my code:
I know This is one of some use case variants in my code:
Hope this helps somehow! |
It seems that there might be some problems because of incompatibilities between kapt and newer Kotlin versions. The solution seems to be to migrate to KSP-based Dagger. @postfixNotation could you maybe try it and report back? |
Hi @serras, Dagger KSP:
Version numbers:
I tried to migrate yesterday again but I still get the same error message. I might be migrating from Dagger back to pure DI since Dagger won't become multiplatform in the foreseeable future. I also watched your keynote about context receivers which was pretty impressive. |
@postfixNotation has this improved with 1.2.4? |
@serras unfortunately it didn't. |
I migrated to the latest version of Arrow which made me add
io.arrow-kt:arrow-resilience
to use the Schedule class.The import statement therefore changed from
arrow.fx.coroutines.Schedule
toarrow.resilience.Schedule
and alsoarrow.fx.coroutines.retry
toarrow.resilience.retry
.I'm using Dagger KSP version
2.49
and KSP version1.9.21-1.0.16
When I build the module I get the following error message:
So actually I cannot fully migrate from 1.1.5 to 1.2.1 using the lastest APIs/import statements.
The text was updated successfully, but these errors were encountered: