Skip to content
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

Regression: is-getter detection error #559

Closed
guai opened this issue Apr 11, 2022 · 3 comments
Closed

Regression: is-getter detection error #559

guai opened this issue Apr 11, 2022 · 3 comments
Labels
to-evaluate Issue that has been received but not yet evaluated

Comments

@guai
Copy link

guai commented Apr 11, 2022

following kotlin class (stripped for simplicity) have been converting to json ok in com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:2.11.4 and causes error Conflicting getter definitions for property "iscsi": Volume#getIscsi() vs Volume#getCsi() in later versions

import io.k8s.api.core.v1.*

open class Volume(
    val csi : CSIVolumeSource?,
    val iscsi : ISCSIVolumeSource?,
)

in java it looks like this

public class Volume {
   public final CSIVolumeSource getCsi() { return this.csi; }
   public final ISCSIVolumeSource getIscsi() { return this.iscsi; }
}

as you can see there is no booleans here. so no is-getters detection logic should be applied, but it seems it does.

@guai guai added the to-evaluate Issue that has been received but not yet evaluated label Apr 11, 2022
@guai guai changed the title Regression: is-getter detection logic applied Regression: is-getter detection error Apr 11, 2022
@guai
Copy link
Author

guai commented Apr 11, 2022

Btw, is there a workaround via mixins?

@cowtowncoder
Copy link
Member

Wrong repo, will transfer to Kotlin module.

@cowtowncoder cowtowncoder transferred this issue from FasterXML/jackson-databind Apr 11, 2022
@k163377
Copy link
Contributor

k163377 commented Mar 4, 2023

This issue will be fixed by #630 and therefore closed as a duplicate.

@k163377 k163377 closed this as completed Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
to-evaluate Issue that has been received but not yet evaluated
Projects
None yet
Development

No branches or pull requests

3 participants