Implement CBOR Extended Diagnostic Notation (EDN) export functionality #31
+6,917
−88
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.
This PR adds support for exporting CBOR data to Extended Diagnostic Notation (EDN) format, a human-readable text representation of CBOR data as specified in the CBOR RFC.
What's Added
The implementation introduces a new
CborEdn
class insrc/cbor/CborEdn.ts
that provides methods to convert JavaScript values and CBOR-encoded data to EDN string format.Core API
Supported Data Types
The implementation handles all CBOR data types with proper EDN representation:
h'...'
) representationtag(content)
)Examples
Testing
The implementation includes comprehensive test coverage:
Documentation
Updated the CBOR module README with EDN usage examples and API documentation.
This is an additive feature that doesn't modify any existing CBOR encoding/decoding logic, ensuring full backward compatibility.
Fixes #30.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.