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
@JsonEnum()
enum SellingStatus {
@JsonValue(1)
value1(1),
@JsonValue(11)
value11(11),
@JsonValue(21)
value21(21),
@JsonValue(31)
value31(31),
/// Default value for all unparsed values, allows backward compatibility when adding new values on the backend.
$unknown(null);
Proposal
I would like the field names to be applied like this according to x-enumNames.
@JsonEnum()
enum SellingStatus {
@JsonValue(1)
�not_listed(1),
@JsonValue(11)
selling(11),
@JsonValue(21)
soldOut(21),
@JsonValue(31)
closed(31),
/// Default value for all unparsed values, allows backward compatibility when adding new values on the backend.
$unknown(null);
The text was updated successfully, but these errors were encountered:
Use case
@JsonEnum()
enum SellingStatus {
@JsonValue(1)
value1(1),
@JsonValue(11)
value11(11),
@JsonValue(21)
value21(21),
@JsonValue(31)
value31(31),
/// Default value for all unparsed values, allows backward compatibility when adding new values on the backend.
$unknown(null);
Proposal
I would like the field names to be applied like this according to x-enumNames.
"SellingStatus": {"enum": [1, 11, 21, 31], "title": "SellingStatus", "type": "integer", "x-enumNames": ["not_listed", "selling", "sold_out", "closed"]}
@JsonEnum()
enum SellingStatus {
@JsonValue(1)
�not_listed(1),
@JsonValue(11)
selling(11),
@JsonValue(21)
soldOut(21),
@JsonValue(31)
closed(31),
/// Default value for all unparsed values, allows backward compatibility when adding new values on the backend.
$unknown(null);
The text was updated successfully, but these errors were encountered: