-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
About: update example to use better practices #641
Conversation
wouldn't no-semicolons be kind of alienating to some users? |
Shouldn't be. Since is the official documentation it should be noted that it will most definitely work, and will prepare people for the inevitable hordes of semicolonless code people will see in various modules. :) |
res.setHeader('Content-Type', 'text/plain') | ||
res.end('Hello World\n') | ||
}) | ||
server.listen(port, hostname, () => { |
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.
can we put one blank line between this line and the previous?
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.
yup
bfa269c
to
2131b1a
Compare
LGTM :) |
pardon me but um
|
nvm I'll just make a test PR then |
@Fishrock123 wow i cant read |
Can we put back the semicolons? I think this is inconsistent with the API docs where semicolons are always used. It's just an OCD of mine, don't want to start yet another semicolons discussion. |
also for testing the latest https://github.com/nodejs-github-bot/github-bot