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
If a map has keys that are not strings but bin format, in nodejs these are parsed as ascii text (or utf8?). However, in the browser these are first stored as a Int8Array, and then turned to strings using toString(), which makes e.g. the key "type" (ascii) look like "116,121,112,101". Either handling would be fine, but the inconsistency is a problem.
My test case is serializing using msgpack-numpy in python and then trying to deserialize using msgpack-lite (note: msgpack-numpy doesn't use an ext type but just produces a map object for some reason, and also uses bin format for the keys, instead of strings, again, for some "reason"...).
The text was updated successfully, but these errors were encountered:
If a map has keys that are not strings but bin format, in nodejs these are parsed as ascii text (or utf8?). However, in the browser these are first stored as a Int8Array, and then turned to strings using toString(), which makes e.g. the key "type" (ascii) look like "116,121,112,101". Either handling would be fine, but the inconsistency is a problem.
My test case is serializing using msgpack-numpy in python and then trying to deserialize using msgpack-lite (note: msgpack-numpy doesn't use an ext type but just produces a map object for some reason, and also uses bin format for the keys, instead of strings, again, for some "reason"...).
The text was updated successfully, but these errors were encountered: