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.
New issue
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
crypto: implement randomuuid #36729
crypto: implement randomuuid #36729
Changes from all commits
27c9d28
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding naming: The function name
randomUUID()
was initially proposed and discussed in tc39/proposal-uuid#3 (comment)We were also discussing renaming the api of the
uuid
npm module (uuidjs/uuid#540 (comment)) but came to the conclusion that we don't want to do that while the standardization efforts are still ongoing.After all I still think the term
randomUUID
has a lot of benefits since it clearly describes what this is about whereas the whole concept of "version" within the UUID RFC has proven to be highly confusing, see my detailed analysis.It also avoids naming conflicts with the current
uuid
npm module so this should remove confusion when upgrading from the npm module to the native implementation.So all in all I'm 👍 for naming it like that in Node.js