Generic uuidv8 parsing support (version, variant, bytes) #19
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
Owner
|
There are some conflicts with |
vheathen
force-pushed
the
uuid8-parsing
branch
from
d321c0d to
5a156f7
Compare
Author
|
I've rebased the branch, conflicts are gone now. |
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.
We are using custom generated uuids v8 in some parts of our project, and we need to parse\validate uuids in general. Depending on a uuid version we use different code paths (uuid v8 are used in a few very specific cases).
We were using
elixir_uuidand recently decided to switch touniq. But currently it doesn't support uuid v8 parsing, so this is the implementation.