eclipse-ee4j / eclipse-ee4j/yasson
Using LinkedHashMap to preserve attribute order
- Dominant language
- Java
- Stars
- 218
- Forks
- 109
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 9
Description
When using a generic approach in our Java model (-> maps), we'd like to preserve the attribute order "as is". So it would be great to configure whether to not order attributes or preserve the given order (perhaps only when using collections/maps).
What do you think about using LikedHashMap as default implementation when PropertyOrderStrategy is set to ANY?
Contributor guide
Research direction
Start by tracing PropertyOrderStrategy through the generic Java model-to-map path and inspect any existing ordering tests. The issue is done when configuration clearly distinguishes unordered output from preserving input order, including the proposed collections/maps behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100