-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
doc: message.header duplication correction #3997
Conversation
single value is represented on the parsed object. | ||
When headers are duplicated, either they're concatenated with `', '`, | ||
only the first one is taken, or they're presented as an array, depending | ||
on the header. See [message.headers][]. |
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 but maybe link directly to message.headers
without trying to describe the logic first? Something like See [message.headers][] for details on how duplicate headers are handled.
That way it can't go out of sync.
LGTM with a suggestion. If other collaborators feel it's good as-is, go ahead and land it. |
I think linking will be the better solution. LGTM other than that |
LGTM with the same comment. |
The old version of the text here was slightly incorrect, so it just defers the details to the section in which they're fully described.
7dc314a
to
dc7fe51
Compare
Cool, shortened it down to just what @bnoordhuis suggested. |
Thanks Bryan, landed in 6f87aa9. |
The old version of the text here was slightly incorrect, so it just defers the details to the section in which they're fully described. PR-URL: #3997 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
The old version of the text here was slightly incorrect, so it just defers the details to the section in which they're fully described. PR-URL: #3997 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
The old version of the text here was slightly incorrect, so it just defers the details to the section in which they're fully described. PR-URL: #3997 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
The old version of the text here was slightly incorrect, so it just defers the details to the section in which they're fully described. PR-URL: #3997 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
The old version of the text here was slightly incorrect, so it just defers the details to the section in which they're fully described. PR-URL: #3997 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
The old version of the text here was slightly incorrect, so it just defers the details to the section in which they're fully described. PR-URL: #3997 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
The old version of the text here was slightly incorrect (probably how it used to work, so it's now it's slightly more vague, deferring the details to the section in which they're already fully described.