This message was deleted.

Trying this:

data class TransferQuoteRequest(
    @JsonProperty("sendCcy")
    val sendCcy: Currency,
    val receiveCcy: Currency,
    val amount: BigDecimal,

    @JsonProperty("isSendCcy")
    val isSendCcy: Boolean
)

Gives:

Conflicting/ambiguous property name definitions (implicit name 'isSendCcy'): found multiple explicit names: [sendCcy, isSendCcy], but also implicit accessor:re

Terminology note: serialize an object into JSON, deserialize from JSON into an object

Interesting. Is it then best to stay away from fields beginning with

is

?

That, combined with the fact that

val

constructor parameters in Kotlin are really expanded to multiple things (a getter, setter, constuctor param, and field) makes for a very confusing situation

Well changing the field name to something else (

amountInSendCcy

) worked fine

Or applying use site targets might help, too (e.g.

@get:JsonProperty("…")

) https://kotlinlang.org/docs/annotations.html#annotation-use-site-targets

Great. Thanks Drew, that’s really helpful

Fair enough; I often see abbreviations overused in an attempt to save bits on the wire when relying on compression (which is almost certainly already, transparently in place0 is a far better solution

Ah I see-- Yeah, we’re not there yet 🙂