Add HexToken case in OptionalContent parsing #971
Merged
Conversation
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
Add HexToken case in OptionalContent parsing
simonedd
changed the title
BobLd
approved these changes
Jan 14, 2025
Contributor
Author
|
Hi, Is there an ETA for the new stable release? Thanks |
Collaborator
|
@simonedd I'm not sure yet, but this month or the following one I'd hope. Also, please note you have pre-release packages available |
This was referenced Sep 16, 2025
This was referenced Sep 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add HexToken case in OptionalContent parsing to fix excepition reported here: #266 (comment)