-
Notifications
You must be signed in to change notification settings - Fork 36
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
MoshiX generates malformed proguard rule #415
Comments
Which version of Kotlinpoet are you using? |
We tried the latest one 1.13.0, but I believe we saw similar with 1.12.0, but not quite sure I have to double check as it might that some other library that uses KPoet updated it to 1.13.0. Btw, the way how we addressed this issue in our project is to avoid using |
Got it. This is a Kotlinpoet bug, so could you please file there? The reflection name should not be escaped |
Yeah, I guess you are right will reference this one in that issue. |
I wasn't able to reproduce this issue with plain KPoet, but have one guess:
That makes me think if there any possible transformation in the codegen that leads to passing I also tried to reproduce the original issue in
even this valid source code, but I guess it should be non escaped package name. I still will try to repro issue we see in our project with escaped proguard rule, but does above ^^^ give any idea where the issue is? |
I did not understand your third bullet, maybe because the formatting broke. Why would you make a class like |
Closing as wontfix as there's been no followup |
Latest version of MoshiX sealed leads to malformed proguard rules.
The cause of issue was the
data
package name like:com.example.data
The generated proguard rule:
Error:
Not 100% sure what the cause of this but it looks like KotlinPoet changed the returned value in
reflectionName()
:MoshiX/moshi-sealed/codegen/src/main/kotlin/dev/zacsweers/moshix/sealed/codegen/ProguardConfig.kt
Line 57 in 612e921
The text was updated successfully, but these errors were encountered: