Hi!
I was looking at some javascript that was behaving differently on Jenkins
than it does on other apps. I boiled it down to the simplest reproducible
test case.
It turned out that serialization was behaving differently when calling
JSON.stringify.
This is the sample code you can run on the Chrome DevTools
JSON.stringify({ a: [1, 2, 3] });
On Jenkins, this is the behavior
'{"a":"[1, 2, 3]"}'
On other apps, this is the behavior
'{"a":[1, 2, 3]}'
When I attempt to debug the code, stepping into `JSON.stringify` on Jenkins
takes me to prototype.js.
I've seen some threads here attempting not to rely on prototype.js for
functionality, but how far are we from removing it?
- Rahul
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/708c6498-e0d4-481e-9ad7-e0a8e5af65ffn%40googlegroups.com.
