-
Notifications
You must be signed in to change notification settings - Fork 7
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
docs: flesh out API and justification for uuid standard library #8
Conversation
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.
Awesome, thanks for getting started on this, I think it's a very good starting point!
In my comments I focused on consistency of terminology and formatting. I bet @broofa will have much more elaborate feedback on the proposed contents 😉
b79540e
to
4fbaa13
Compare
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.
LGTM once the built-in
vs. builtin module
vs. JavaScript standard library module
confusion has been resolved.
Feeling inspired by TC39, and by the statistics @ctavan pulled together, I've started to flesh out the API for the
uuid
built-in module.I've also made an effort to start to outline why I think looking at community practices on npm, and using these to help inspire built-in modules, is valuable.