-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Closed
Description
Although property index was added in Jackson 2.4, and is used for some purposes (such as integer field id for protobuf), it is not yet (as of 2.10) used for ordering properties in other contexts. But it probably should be: there are already requests to use it for CSV headers, for example, and it seems reasonable that ordering would be based on combination of things so that:
- Explicit ordering (via
@JsonPropertyOrder) would have highest priority @JsonProperty.indexshould be used after this- Possible alphabetic ordering for things not covered by (1) or (2)
It may become necessary to allow NOT doing this, too (via MapperFeature), but let's start by assumption that index should be used.
Metadata
Metadata
Assignees
Labels
No labels