-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
It seems that transit-js Map constructor handling of its parameter is non-standard. The spec says it is an iterable of 2-element (key, value) arrays. The transit-js Map constructor expects an iterable of alternating key-value pairs.
I imagine it would be disruptive to change the behavior of the Map constructor at this point, but maybe it's at least worth highlighting the non-conformance with the ECMA spec in the API docs?
Metadata
Metadata
Assignees
Labels
No labels