feat(cbor): add encoding/decoding for new Map()
instance
#6252
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #6249
These changes adds support for accepting a Map instance in
encodeCbor
and returning it again fromdecodeCbor
. It achieves this via the 259 tag number (Spec).While the code is mostly the same for encoding and decoding Objects, it differs in the need for limiting keys to only strings. It also guarantees that the order isn't at risk of being changed due to encoding/decoding.
This pull request does not add support for accepting Map instances via the streaming methods of this library. The logistics for decoding that is a bit more trickier to figure out.