Repository navigation
Print CBOR_TYPE_BYTESTRING value as hex string - #281
Merged
Merged
Conversation
Owner
|
Thank you! |
PJK
added a commit
that referenced
this pull request
Jun 3, 2023
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this pull request
Feb 4, 2024
0.11.0 (2024-02-04) --------------------- - [Updated documentation to refer to RFC 8949](PJK/libcbor#269) - Improvements to `cbor_describe` - [Bytestring data will now be printed as well](PJK/libcbor#281) by [akallabeth](https://github.com/akallabeth) - [Formatting consistency and clarity improvements](PJK/libcbor#285) - [Fix `cbor_string_set_handle` not setting the codepoint count](PJK/libcbor#286) - BREAKING: [`cbor_load` will no longer fail on input strings that are well-formed but not valid UTF-8](PJK/libcbor#286) - If you were relying on the validation, please check the result using `cbor_string_codepoint_count` instead - BREAKING: [All decoders like `cbor_load` and `cbor_stream_decode` will accept all well-formed tag values](PJK/libcbor#308) (bug discovered by [dskern-github](https://github.com/dskern-github)) - Previously, decoding of certain values would fail with `CBOR_ERR_MALFORMATED` or `CBOR_DECODER_ERROR` - This also makes decoding symmetrical with serialization, which already accepts all values
msk
pushed a commit
to msk/pkgsrc
that referenced
this pull request
May 11, 2026
0.11.0 (2024-02-04) --------------------- - [Updated documentation to refer to RFC 8949](PJK/libcbor#269) - Improvements to `cbor_describe` - [Bytestring data will now be printed as well](PJK/libcbor#281) by [akallabeth](https://github.com/akallabeth) - [Formatting consistency and clarity improvements](PJK/libcbor#285) - [Fix `cbor_string_set_handle` not setting the codepoint count](PJK/libcbor#286) - BREAKING: [`cbor_load` will no longer fail on input strings that are well-formed but not valid UTF-8](PJK/libcbor#286) - If you were relying on the validation, please check the result using `cbor_string_codepoint_count` instead - BREAKING: [All decoders like `cbor_load` and `cbor_stream_decode` will accept all well-formed tag values](PJK/libcbor#308) (bug discovered by [dskern-github](https://github.com/dskern-github)) - Previously, decoding of certain values would fail with `CBOR_ERR_MALFORMATED` or `CBOR_DECODER_ERROR` - This also makes decoding symmetrical with serialization, which already accepts all values
jperkin
pushed a commit
to TritonDataCenter/pkgsrc
that referenced
this pull request
May 14, 2026
0.11.0 (2024-02-04) --------------------- - [Updated documentation to refer to RFC 8949](PJK/libcbor#269) - Improvements to `cbor_describe` - [Bytestring data will now be printed as well](PJK/libcbor#281) by [akallabeth](https://github.com/akallabeth) - [Formatting consistency and clarity improvements](PJK/libcbor#285) - [Fix `cbor_string_set_handle` not setting the codepoint count](PJK/libcbor#286) - BREAKING: [`cbor_load` will no longer fail on input strings that are well-formed but not valid UTF-8](PJK/libcbor#286) - If you were relying on the validation, please check the result using `cbor_string_codepoint_count` instead - BREAKING: [All decoders like `cbor_load` and `cbor_stream_decode` will accept all well-formed tag values](PJK/libcbor#308) (bug discovered by [dskern-github](https://github.com/dskern-github)) - Previously, decoding of certain values would fail with `CBOR_ERR_MALFORMATED` or `CBOR_DECODER_ERROR` - This also makes decoding symmetrical with serialization, which already accepts all values
tsutsui
pushed a commit
to tsutsui/pkgsrc
that referenced
this pull request
Oct 17, 2026
0.11.0 (2024-02-04) --------------------- - [Updated documentation to refer to RFC 8949](PJK/libcbor#269) - Improvements to `cbor_describe` - [Bytestring data will now be printed as well](PJK/libcbor#281) by [akallabeth](https://github.com/akallabeth) - [Formatting consistency and clarity improvements](PJK/libcbor#285) - [Fix `cbor_string_set_handle` not setting the codepoint count](PJK/libcbor#286) - BREAKING: [`cbor_load` will no longer fail on input strings that are well-formed but not valid UTF-8](PJK/libcbor#286) - If you were relying on the validation, please check the result using `cbor_string_codepoint_count` instead - BREAKING: [All decoders like `cbor_load` and `cbor_stream_decode` will accept all well-formed tag values](PJK/libcbor#308) (bug discovered by [dskern-github](https://github.com/dskern-github)) - Previously, decoding of certain values would fail with `CBOR_ERR_MALFORMATED` or `CBOR_DECODER_ERROR` - This also makes decoding symmetrical with serialization, which already accepts all values
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Add data as hex string in
cbor_describefor typeCBOR_TYPE_BYTESTRINGI did find it useful to have the data printed out just like for
CBOR_TYPE_STRING.