Replies: 2 comments 5 replies
-
I'd file the the bug against Rhino https://github.com/mozilla/rhino/issues |
Beta Was this translation helpful? Give feedback.
-
This is now fixed in the Rhino snapshot builds. Your test cases are part of the test suite https://github.com/mozilla/rhino/blob/189b1096fced52490ddc96ea854210e7a3d7497e/testsrc/jstests/json-stringify-array-replacer.jstest I don't know if mirth would include a snapshot build or if they will wait for the next official release. There's been quite a bit of change since Rhino 1.7.12, which is what mirth 3.10 and 3.11 use. Rhino 1.7.13 was released last September (before mirth 3.10.) This fix will be in Rhino 1.7.14. I don't know of an official release date for that, but the releases just seem to be a tag on the current state of the master branch more than a planned thing. |
Beta Was this translation helpful? Give feedback.
-
I'm using Mirth v3.10.1 with ES6 (Rhino language version 200) but also tested with lower Mirth v3.5.2
I experienced a bug in Mirth (Rhino) with
JSON.stringify()
function when you provide an array of strings as 2nd argument that is used as a whitelist for the property names that you want to keep and if the property names are numbers as strings. You can see a full code example here and compare Mirth/Rhino result with any other JS engine (browser):https://js.do/code/rhino-issue-object-keys-stringnumber-keys
Summary:
I also tried in Rhino shell with the same result. It took me hours to find why Rhino returns
{}
...Any idea how to tackle this?
Beta Was this translation helpful? Give feedback.
All reactions