-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add AnnotationIntrospector.findRenameByField()
to support Kotlin's "is-getter" naming convention
#2527
Comments
MapperFeature
to support Kotlin's "is-getters"MapperFeature
to support Kotlin's "is-getters"
Note: filed #2571 as something that might solve this with more general mechanism. |
MapperFeature
to support Kotlin's "is-getters"AnnotationIntrospector.findRenameByField()
to support Kotlin's "is-getter" naming convention
After wrestling with this for a bit -- trying not to add a new (too) specific Will need to verify with |
(note: follow up for FasterXML/jackson-module-kotlin#80)
So, Kotlin generates its property accessors, fields similar to (but not identical) Bean conventions:
https://kotlinlang.org/docs/reference/java-to-kotlin-interop.html
and as a result Jackson's default introspection has some trouble, in particular for "is getters".
While there is now a patch for Kotlin, it might make sense to add a
MapperFeature
to enable it at lower level -- both for being bit more optimal, and to avoid possible regression when databind introspection changes in future (for 3.0 in particular).The text was updated successfully, but these errors were encountered: