You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(note: continuation of [some issue but wrote originally down wrong])
Although @JsonValue is currently only used for serialization purposes, it seems it could be used for deciding on one otherwise ambiguous use case: that of 1-argument Creator method without mode property.
This case currently uses heuristics, such that:
If there is explicit name specified for Creator argument (like @JsonProperty), Mode.PROPERTIES is used
If there is a named non-creator-property matching Creator argument name, Mode.PROPERTIES is used -- this is typically the case for Record types
Otherwise Mode.DELEGATING is used (unless different default choice specified)
However: use of @JsonValue would strongly suggest that as the second step (after explicit name for Creator argument) we should consider its existence to select Mode.DELEGATING instead.
The text was updated successfully, but these errors were encountered:
(note: continuation of [some issue but wrote originally down wrong])
Although
@JsonValue
is currently only used for serialization purposes, it seems it could be used for deciding on one otherwise ambiguous use case: that of 1-argument Creator method withoutmode
property.This case currently uses heuristics, such that:
@JsonProperty
),Mode.PROPERTIES
is usedMode.PROPERTIES
is used -- this is typically the case for Record typesMode.DELEGATING
is used (unless different default choice specified)However: use of
@JsonValue
would strongly suggest that as the second step (after explicit name for Creator argument) we should consider its existence to selectMode.DELEGATING
instead.The text was updated successfully, but these errors were encountered: