Skip to content

decode CBOR's undefined to null #44

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.

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

Merged
merged 1 commit into from
Nov 20, 2018

Conversation

Stebalien
Copy link
Contributor

Bleh. We're not going to round-trip this but we shouldn't hit this anyways.

Alternatively, we could just return an error. However, that may break things for some users...

fixes #43

(needs test)

Bleh. We're not going to round-trip this but we shouldn't hit this anyways.

Alternatively, we could just return an error. However, that may break things for
some users...

fixes polydawn#43
@warpfork
Copy link
Member

Ouch 🤕 🌴

I hardly even remember transcribing the "undefined" constant from the spec.

I guess this is as reasonable as any other behavior for a value that is, IMO, fundamentally pretty unreasonable...

@warpfork warpfork merged commit ede3ae2 into polydawn:master Nov 20, 2018
@warpfork
Copy link
Member

^ dragged it along in #45 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fails to decode a valid CBOR object
2 participants