We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The stduuid library hasn't seen active development in a while, so it'll have to be a custom addition (can replace later).
stduuid
Roadmap:
uuid.v7
isCanonical
RFC_STRING_PATTERN
In the long term, the UUID library/bindings need a bit of a redesign. This can wait until the RFC is standardized, however.
There's also potential security concerns - see RFC: https://www.rfc-editor.org/rfc/rfc9562#name-timestamp-considerations These may or may not be important enough to warrant taking them into account when settling on a "stable" implementation.
However, for now just getting something usable will suffice. I want to experiment with the v7 format before going any further.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The
stduuid
library hasn't seen active development in a while, so it'll have to be a custom addition (can replace later).Roadmap:
uuid.v7
as a separate, experimental generator (incompatible withisCanonical
andRFC_STRING_PATTERN
)In the long term, the UUID library/bindings need a bit of a redesign. This can wait until the RFC is standardized, however.
There's also potential security concerns - see RFC: https://www.rfc-editor.org/rfc/rfc9562#name-timestamp-considerations
These may or may not be important enough to warrant taking them into account when settling on a "stable" implementation.
However, for now just getting something usable will suffice. I want to experiment with the v7 format before going any further.
The text was updated successfully, but these errors were encountered: