You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the latest chrome, when using the editor with the following JSON;
{
"reg_definition": {
"reg_name": "DATA",
"reg_description": "Data from the last SETUP packet. It will be 10 bytes long, because it will include the CRC16. This is a FIFO; use `DATA_ACK` to advance the queue.",
"reg": [
{ "name": "DATA", "bits": 8, "attr": "RO", "description": "The next byte of SETUP data" }
]
}
}
I get the following error in the Chrome console;
Uncaught TypeError: e.charCodeAt is not a function
at t.exports (wavedrom.min.js:3)
at t.exports (wavedrom.min.js:3)
at t.exports (wavedrom.min.js:3)
at t.exports (wavedrom.min.js:3)
at t.exports (wavedrom.min.js:3)
at t.exports (wavedrom.min.js:3)
at Object.t.exports [as EditorRefresh] (wavedrom.min.js:3)
at c (init.js:129)
The text was updated successfully, but these errors were encountered:
I just ran into this issue after upgrading wavedrom -- the older version worked, but the newer version silently failed with only that error in the console -- TypeError: e.charCodeAt is not a function
Could there be a more descriptive error generated when JSON isn't valid? In this case, there were trailing commas, which wavedrom apparently used to accept but now no longer does.
On the latest chrome, when using the editor with the following JSON;
I get the following error in the Chrome console;
The text was updated successfully, but these errors were encountered: