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.

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

MessagePack Proposal v5 with explicit string type. #8

Merged
merged 6 commits into from
Jul 26, 2015

Conversation

chakrit
Copy link
Contributor

@chakrit chakrit commented Aug 14, 2013

Reference: https://gist.github.com/frsyuki/5432559#types-extension-type
GH Issue: #7

  • Reorder decoder types detection code so it aligns with mapping tables in the specs.
  • Changed how undefined are handled, uses the fixext 1 extension type instead.
  • Removed old raw-related things.
  • Added support for str type family decoded to node string.
  • Added support for bin type family decoded to node Buffer.
  • Added support for ext and fixext type family decoded to a [type, Buffer] tuple.
    • Exception for fixext 1 which is just 1-byte long so a simple [type, value] is
      returned instead.
  • TODO: There is no test for the ext and fixext since there is no way/need in JS to
    specify and encode "extension" type. Would be good to have tests on decoding part though
    since other languages/implementation may have made use of them.

Reference: https://gist.github.com/frsyuki/5432559#types-extension-type

* Reorder decoder types detection code so it aligns with mapping tables in the specs.
* Changed how `undefined` are handled, uses the `fixext 1` extension type instead.
* Removed old `raw`-related things.
* Added support for `str` type family decoded to node string.
* Added support for `bin` type family decoded to node Buffer.
* Added support for `ext` and `fixext` type family decoded to a [type, Buffer] tuple.
  * Exception for `fixext 1` which is just 1-byte long so a simple [type, value] is
    returned instead.
* TODO: There is no test for the `ext` and `fixext` since there is no way/need in JS to
  specify and encode "extension" type. Would be good to have tests on decoding part though
  since other languages/implementation may have made use of them.
@chakrit
Copy link
Contributor Author

chakrit commented Aug 20, 2013

@doughsay
Copy link

doughsay commented Jun 2, 2015

Could this help #15?

@creationix
Copy link
Owner

@doughsay I would expect that to fix it. I wonder if @chakrit still wants to merge.

@creationix
Copy link
Owner

@nkzawa
Copy link

nkzawa commented Jul 6, 2015

👍

@chakrit
Copy link
Contributor Author

chakrit commented Jul 6, 2015

Wow, I've almost forgotten this PR, it has been so long. Also buried under a pile of other GH notifications.

I'll try to get this mergeable tonight, hopefully.

@nkzawa
Copy link

nkzawa commented Jul 6, 2015

@chakrit cool 😄

@chakrit
Copy link
Contributor Author

chakrit commented Jul 25, 2015

@creationix @nkzawa I've merged master back into my fork and gotten rid of the only README conflict.

npm test passes but I have lost access to the project that was in need of this so let me know if anything else should be done.

creationix added a commit that referenced this pull request Jul 26, 2015
MessagePack Proposal v5 with explicit string type.
@creationix creationix merged commit 36c0ce2 into creationix:master Jul 26, 2015
@skerit skerit mentioned this pull request Mar 17, 2018
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.

5 participants