You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to add an option to explicitly define definite/indefinite list length and also to maintain this context when parsing CBOR.
Context: I am performing cryptographic operations and hashing on CBOR data. The fact that HexEncodedCbor -> CborValue -> HexEncodedCbor yields a different result compared to the input is causing me problems and making stuff harder to test. Also I often need to make additive changes to CBOR. But doing this and re-encoding the CBOR turns some indefinite lists into a definite lists.
P.S. I am happy to help with this work. I just wanted to know whether you would accept merging a PR for it. Otherwise I'd just fork this and maintain a separate copy myself.
The text was updated successfully, but these errors were encountered:
Hello,
I would like to add an option to explicitly define definite/indefinite list length and also to maintain this context when parsing CBOR.
Context: I am performing cryptographic operations and hashing on CBOR data. The fact that HexEncodedCbor -> CborValue -> HexEncodedCbor yields a different result compared to the input is causing me problems and making stuff harder to test. Also I often need to make additive changes to CBOR. But doing this and re-encoding the CBOR turns some indefinite lists into a definite lists.
P.S. I am happy to help with this work. I just wanted to know whether you would accept merging a PR for it. Otherwise I'd just fork this and maintain a separate copy myself.
The text was updated successfully, but these errors were encountered: