Implement CBOR date tags according to RFC 8943 #29
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 comprehensive support for CBOR date tags as specified in RFC 8943 "Tags for Date". JavaScript
Date
objects are now automatically encoded and decoded using CBOR date tags, providing seamless date handling in CBOR serialization.Features Added
Automatic Date Encoding/Decoding:
Date
objects are automatically encoded using tag 100 (days since epoch) for maximum compactnessDate
objects during decodingRFC 8943 Compliance:
Robust Error Handling:
JsonPackExtension
objectsUsage Examples
Basic Usage:
Manual Tag Usage:
Utility Functions:
Implementation Details
The implementation handles complex scenarios including dates in nested objects, arrays of dates, leap years, historical dates (before 1970), and future dates, ensuring robust date serialization across all use cases.
Fixes #28.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.