We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, when you've loaded an object like the following in tree mode:
tree
{ "one": 1, "three": 3 }
and afterwards update this object to the following using editor.update(...):
editor.update(...)
{ "one": 1, "two": 2, "three": 3 }
The new property "two" is added at the end of the rendered fields instead of inserted in the middle: you get the order "one", "three", "two".
"two"
"one"
"three"
It would be neat if the newly added field is inserted in the middle instead, maintaining order of the keys.
For reference: #891 (comment)
The text was updated successfully, but these errors were encountered:
2316c87
Fix #917, #926: update ordering of object keys
b09dbca
This is fixed now in jsoneditor@8.6.2 and web application v5.3.3.
jsoneditor@8.6.2
v5.3.3
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Currently, when you've loaded an object like the following in
tree
mode:and afterwards update this object to the following using
editor.update(...)
:The new property
"two"
is added at the end of the rendered fields instead of inserted in the middle: you get the order"one"
,"three"
,"two"
.It would be neat if the newly added field is inserted in the middle instead, maintaining order of the keys.
For reference: #891 (comment)
The text was updated successfully, but these errors were encountered: