2.7.0 release bug
See original GitHub issueGeneral information
- json-editor version: 2.7.0
Expected behavior: existing production page to load without error (like it did in 2.6.1)
Actual behavior: Uncaught TypeError
can’t define value after a editor is defined
Steps to reproduce the behavior
- load any schema that has a dropdown with name
root.PROJECT
and defined it asEproject
then try to overwrite the value withgetEditor
Eproject = new JSONEditor(document.getElementById('Eproject'),{schema: data});
Eproject.getEditor('root.PROJECT').setValue("some new val")
generates the following error on load in 2.7.0, this does not occur on 2.6.1
Uncaught TypeError: Eproject.getEditor(...) is undefined
Issue Analytics
- State:
- Created a year ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Fixes for 2.7.0 release · Issue #2371 · svaarala/duktape - GitHub
Yaml safe_load() in tooling Use py yaml.safe_load() instead of load() #2384; Void pointer arithmetic in duk_alloc_pool.c Avoid void ptr ...
Read more >2.7.0 - pfSense bugtracker
2.7.0. open. Future pfSense CE software release ... Bug #3132: Gateway events for IPv6 affect IPv4 services and vice versa, Actions.
Read more >Spring Boot 2.7.0 available now
0 has been released and is available from Maven Central. This release adds a significant number of new features and improvements. For full ......
Read more >Release Notes - Kafka - Version 2.7.0
Bug. [KAFKA-6078] - Investigate failure of ReassignPartitionsClusterTest. ... useless condition when a field is made nullable and flexible version is used ...
Read more >Bug Fixes in This Version - NVIDIA Networking Docs
Fixed in Release: 2.7.0. 2972970. Description: Fixed the issue where completion of SHARP installation using sharp_daemons_setup.sh script ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am trying to reproduce the error but all seems to work like it should. Can you provide a complete example that i can use to reproduce this? With complete i mean, the simplest schema that trigger the error and, the javascript used to init the editor and if set the initial data too. Thanks and sorry for the inconvenience
Well that solved it. Must be that 2.6.1 was a little quicker, and won the race, so it worked. You may want to put in a warning to the console, if possible. Thank you