Skip to content

Use "body with type" from #1392 throughout spec #1410

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

Jump to bottom
Closed
lucacasonato opened this issue Mar 10, 2022 · 0 comments · Fixed by #1439
Closed

Use "body with type" from #1392 throughout spec #1410

lucacasonato opened this issue Mar 10, 2022 · 0 comments · Fixed by #1439
Labels
clarification Standard could be clearer

Comments

@lucacasonato
Copy link
Member

Currently (safely) extract a body returns a mime type and a body. #1392 introduces a new tuple type for the combo of these two types. We should switch to using it for the extract a body return type and other relevant fields after #1392 lands.
@lucacasonato lucacasonato mentioned this issue Mar 10, 2022
Merged
3 tasks
@annevk annevk added the clarification Standard could be clearer label Mar 10, 2022
@lucacasonato lucacasonato mentioned this issue May 11, 2022
Merged
annevk pushed a commit that referenced this issue May 11, 2022
@lucacasonato
Editorial: consistently use a body + type tuple
3ab5102 
Previously multiple functions returned ad-hoc tuples of body + mime type. This commit consolidates all of these into a concrete "body with type" tuple.

Downstream: whatwg/xhr#349.

Closes #1410.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
clarification Standard could be clearer
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Editorial: consistently use a body + type tuple lucacasonato/fetch
2 participants
@annevk @lucacasonato