Open tw4l opened 1 year ago
Related to https://github.com/webrecorder/specs/issues/141
warcio.js and pywb have slightly different behavior in terms of how keys are handled.
For example for an input {"a": [[], {}, true, false, null, "", " ", 1, 1.0, -0.0]}, we get the following results in warcio vs pywb:
{"a": [[], {}, true, false, null, "", " ", 1, 1.0, -0.0]}
jsonToQueryString
2=true&3=false&5=&6=+&7=1&8=1&9=0
a=True&a.2_=False&a.3_=None&a.4_=&a.5_=+&a.6_=1&a.7_=1.0&a.8_=-0.0
There are two key differences:
a
warcio.js
JSON.stringify
Related to https://github.com/webrecorder/specs/issues/141
warcio.js and pywb have slightly different behavior in terms of how keys are handled.
For example for an input
{"a": [[], {}, true, false, null, "", " ", 1, 1.0, -0.0]}, we get the following results in warcio vs pywb:warcio's
jsonToQueryString2=true&3=false&5=&6=+&7=1&8=1&9=0pywb
a=True&a.2_=False&a.3_=None&a.4_=&a.5_=+&a.6_=1&a.7_=1.0&a.8_=-0.0There are two key differences:
akey is getting lost bywarcio.jsdue to our current implementation of a replacer function passed toJSON.stringify. This needs to be addressed to consider full key paths.