Skip to content
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

Initial unicode baggage keys #117

Closed
wants to merge 5 commits into from
Closed

Conversation

dyladan
Copy link
Member

@dyladan dyladan commented Apr 11, 2023

There are several TODOs in the text including transcribing the rest of the ECMAScript definition into EBNF. This provides a starting point for discussion within the working group.

TODO in followup:

  • Also allow unicode in values. Currently limited to ASCII. All the same arguments apply (maybe more so)

Preview | Diff

@dyladan dyladan marked this pull request as draft April 11, 2023 18:30
@yurishkuro
Copy link
Member

Where can I see the motivation / justification for extending the spec this way (and creating the corresponding complexity)?

@dyladan
Copy link
Member Author

dyladan commented Apr 12, 2023

Where can I see the motivation / justification for extending the spec this way (and creating the corresponding complexity)?

There was significant discussion in #99. This is a draft in order to gauge how much complexity is actually added. Yesterday at the working group meeting we actually discussed the idea of linking directly to an outside spec (like ECMAScript) for the definition instead of writing it ourselves.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants