2.10.0 #4108
Replies: 1 comment 4 replies
-
|
Can I use ksp for response-type-keeper? |
Beta Was this translation helpful? Give feedback.
-
|
No. There is no KSP implementation. |
Beta Was this translation helpful? Give feedback.
-
Well, I used KSP anyway before reading your reply and my app fully compiled. I guess this line had no effect for my app. I just had to use |
Beta Was this translation helpful? Give feedback.
-
|
That line will have no effect, correct. It basically puts the annotation processor on the KSP classpath, but since there's no KSP processor it basically just gets ignored. For a Kotlin project you would need to use |
Beta Was this translation helpful? Give feedback.
-
Thank you, I'll try that. |
Beta Was this translation helpful? Give feedback.
-
New
Support using
Unitas a response type. This can be used for non-body HTTP methods likeHEADor body-containing HTTP methods likeGETwhere the body will be discarded without deserialization.kotlinx.serialization converter!
This was imported from github.com/JakeWharton/retrofit2-kotlinx-serialization-converter/ and remains unchanged from its 1.0.0 release.
The Maven coordinates are
com.squareup.retrofit2:converter-kotlinx-serialization.JAXB 3 converter!
The Maven coordinates are
com.squareup.retrofit2:converter-jaxb3.@Header,@Headers, and@HeaderMapcan now set non-ASCII values through theallowUnsafeNonAsciiValuesannotation property. These are not technically compliant with the HTTP specification, but are often supported or required by services.Publish a BOM of all modules. The Maven coordinates are
com.squareup.retrofit2:retrofit-bom.Invocationnow exposes the serviceClass<?>and the instance on which the method was invoked. This disambiguates the source when service inheritence is used.A response type keeper annotation processor is now available for generating shrinker rules for all referenced types in your service interface. In some cases, it's impossible for static shrinker rules to keep the entirety of what Retrofit needs at runtime. This annotation processor generates those additional rules. For more info see its README.
Changed
Call,Response, etc.) which are used via reflection at runtime.Retrofit.createfunction now has a non-null lower bound. Even if you specified a nullable type before this function would never return null.Throwablesubtypes (not justExceptionsubtypes) to avoid Java'sUndeclaredThrowableExceptionwhen thrown synchronously.suspend funfunctions that returnCall<Body>. These are never correct, and should declare a return type ofBodydirectly.create(ObjectMapper, MediaType)overload to supply the value of theContent-Typeheader for your format.Fixed
This discussion was created from the release 2.10.0.
Beta Was this translation helpful? Give feedback.
All reactions