-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Preserve property order to and from JSON Schema #336
Labels
Comments
Depends on #646 |
Hi schani, are there any plans to fix this in the near future? If not I would try to solve the issue. |
amorscher
added a commit
to amorscher/quicktype
that referenced
this issue
Nov 14, 2019
-if propertyOrder array is available on an object use index of the array as order for bindings -default behavior(alphabetic order) preserved when no particular order is provided
amorscher
added a commit
to amorscher/quicktype
that referenced
this issue
Nov 14, 2019
-if propertyOrder array is available on an object use index of the array as order for bindings -default behavior(alphabetic order) preserved when no particular order is provided
amorscher
added a commit
to amorscher/quicktype
that referenced
this issue
Nov 14, 2019
-if propertyOrder array is available on an object use index of the array as order for bindings -default behavior(alphabetic order) preserved when no particular order is provided
amorscher
added a commit
to amorscher/quicktype
that referenced
this issue
Nov 14, 2019
-if propertyOrder array is available on an object use index of the array as order for bindings -default behavior(alphabetic order) preserved when no particular order is provided
schani
added a commit
that referenced
this issue
May 29, 2020
Added possibility to specify order in JSON-Schema #336
@schani |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're using Javascript objects to represent JSON Schema, so we end up with essentially random order. I think I'd like to keep using objects, but represent the keys as an array of name-type pairs, instead of as an object that maps from names to types. That means for JSON Schema input we'll have to manually parse the data, and for output we might have to just print the JSON ourselves.
The text was updated successfully, but these errors were encountered: