Skip to content

Allow re-casing when serializing for transmission #926

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.

Sign up for GitHub

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

Merged
lukewagner merged 3 commits into from
Jul 31, 2026
Merged

Allow re-casing when serializing for transmission #926

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
53b16b1
Allow re-casing when serializing for transmission
cceckman-at-fastly Jun 4, 2026
7b90e66
Merge branch 'main' into cceckman/case
cceckman-at-fastly Jul 7, 2026
3be0bf9
Merge branch 'main' into cceckman/case
cceckman-at-fastly Jul 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions proposals/http/wit-0.3.0-draft/types.wit
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,8 +178,9 @@ interface types {
///
/// A `fields` resource should store `field-name`s and `field-value`s in their
/// original casing used to construct or mutate the `fields` resource. The `fields`
/// resource should use that original casing when serializing the fields for
/// transport or when returning them from a method.
/// resource should use that original casing when returning them from a method.
/// The `fields` resource may use a different casing when serializing the value
/// for transmission.
///
/// Implementations may impose limits on individual field values and on total
/// aggregate field section size. Operations that would exceed these limits
Expand Down