Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deterministic ordering of maps in the OpenAPI response. #3475

Closed
eak24 opened this issue Mar 13, 2020 · 2 comments
Closed

Deterministic ordering of maps in the OpenAPI response. #3475

eak24 opened this issue Mar 13, 2020 · 2 comments

Comments

@eak24
Copy link
Contributor

eak24 commented Mar 13, 2020

I've found that the ordering of the schemas and the paths can appear to be pretty random. It would be nice if these would be always alphabetically ordered... I will try switching all LinkedHashMaps and the like to be TreeMaps and see how it goes in a PR. Unless there is some profound meaning to return everything in the insertionOder? I can't imagine there is, since the read method takes in what could be an unordered set.

@eak24
Copy link
Contributor Author

eak24 commented Mar 13, 2020

@frantuma here's another PR that should help me fix all the other tests in #3469 by clarifying the failures if there are any - because #3469 seems to switch insertion order by being more efficient in not re-processing types multiple times.

@frantuma
Copy link
Member

frantuma commented Dec 3, 2020

A solution has been implemented in #3740, see PR comment for details and usage scenarios. Closing this ticket, any further issues in this area should be reported in a new or not closed ticket.

@frantuma frantuma closed this as completed Dec 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants