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
According to API docs onChange, onChangeJSON and onChangeText are triggered only by user interactions and not by any programmatic changes.
Expected: Enabling sortObjectKeys should not cause any onChange to be triggered
Actual: Enabling sortObjectKeys causes many onChange calls (I guess one per order-change)
jsoneditor version: 8.6.1
Maybe this is related to #583
The text was updated successfully, but these errors were encountered:
Thanks for reporting Oren, the onChange should indeed not be triggered by enabling sortObjectKeys, this is a bug.
sortObjectKeys
Sorry, something went wrong.
87d320e
This is fixed now in v8.6.4.
v8.6.4
Successfully merging a pull request may close this issue.
According to API docs onChange, onChangeJSON and onChangeText are triggered only by user interactions and not by any programmatic changes.
Expected:
Enabling sortObjectKeys should not cause any onChange to be triggered
Actual:
Enabling sortObjectKeys causes many onChange calls (I guess one per order-change)
jsoneditor version: 8.6.1
Maybe this is related to #583
The text was updated successfully, but these errors were encountered: