refactor: rename header and types to field #557
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is in matching with the new HTTP Semantics RFC 9110
neoeinstein
force-pushed
the
rename-header-to-field
branch
from
0abc28b
to
d86d18a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is in matching with the new HTTP Semantics RFC 9110.
This PR is in draft form. The type renaming and creation of deprecated aliases has been done and compiles, but documentation, usage, and variable names will need to be updated to identify fields and make it more undertandable that fields includes both headers and trailers.
Presuming that deprecation warnings are not considered build failures in downstream builds, this should not be a breaking change.