Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

http: remove CRLF variable #40101

Closed
wants to merge 1 commit into from
Closed

Conversation

shfshanyue
Copy link
Contributor

No description provided.

@nodejs-github-bot nodejs-github-bot added http Issues or PRs related to the http subsystem. needs-ci PRs that need a full CI run. labels Sep 14, 2021
@Trott
Copy link
Member

Trott commented Sep 14, 2021

Welcome, @shfshanyue, and thanks for the pull request.

I don't feel terribly strongly about this, but I'm not convinced CRLF is better than \r\n. To me at least, \r\n is explicit and clear. CRLF seems to be a variable-for-a-variable's sake and not significantly easier to understand. It's possible that I'm missing a nuance here, but I wonder if it wouldn't be better to go the other way and change all the usage of CRLF to \r\n. But I'll leave that up to the @nodejs/http folks. I'm happy to defer to others on something like this.

@mscdex
Copy link
Contributor

mscdex commented Sep 14, 2021

FWIW I'm not particularly fond of having a CRLF string variable either. It'd be better to just include the literal value where needed.

@shfshanyue
Copy link
Contributor Author

I think it would be better if change all the usage of CRLF to \r\n... I'll replace CRLF with \r\n and remove variable CRLF if necessary.

@mcollina
Copy link
Member

I prefer an explicit \r\n as well

@shfshanyue shfshanyue changed the title http: replace \r\n with CRLF http: remove CRLF variable Sep 14, 2021
@shfshanyue shfshanyue force-pushed the master branch 2 times, most recently from a624067 to e63733b Compare September 14, 2021 12:35
Copy link
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Copy link
Member

@mhdawson mhdawson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Ayase-252 Ayase-252 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. request-ci Add this label to start a Jenkins CI on a PR. labels Sep 14, 2021
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Sep 14, 2021
@nodejs-github-bot

This comment has been minimized.

@lpinca
Copy link
Member

lpinca commented Sep 14, 2021

No objections, but please do not change it again after this lands. Refs: f4d3d12

@nodejs-github-bot
Copy link
Collaborator

@VoltrexKeyva VoltrexKeyva removed the needs-ci PRs that need a full CI run. label Sep 16, 2021
mhdawson pushed a commit that referenced this pull request Sep 16, 2021
PR-URL: #40101
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
@mhdawson
Copy link
Member

Landed in e9fc678

BethGriggs pushed a commit that referenced this pull request Sep 21, 2021
PR-URL: #40101
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
BethGriggs pushed a commit that referenced this pull request Sep 21, 2021
PR-URL: #40101
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Michael Dawson <midawson@redhat.com>
@BethGriggs BethGriggs mentioned this pull request Sep 21, 2021
1 task
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. http Issues or PRs related to the http subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants