Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The decoder should support more than integer or string keys for maps #2

Closed
shamblett opened this issue Apr 11, 2017 · 2 comments
Closed

The decoder should support more than integer or string keys for maps #2

shamblett opened this issue Apr 11, 2017 · 2 comments
Assignees
@shamblett

Comments

@shamblett
Copy link
Owner

Currently the decoder restricts map keys to be of integer or string type by specifically checking for these, this should be looked at, CBOR allows more than this, especially negative integers etc. See section 3.7 of RFC7049.
@shamblett shamblett self-assigned this Apr 11, 2017
@shamblett
Copy link
Owner Author

OK, merged your PR for this #24, got rid of the vscode stuff and just bumped the version, otherwise looks good.

Package re published at version 4.1.0

@samigimix samigimix mentioned this issue Oct 1, 2021
Closed
@nicbn
Copy link
Contributor

nicbn commented Jan 18, 2022

Implemented at #38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shamblett shamblett

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shamblett @nicbn