Skip to content

spec: Throw a TypeError if all fields are missing. #50

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

Merged
merged 2 commits into from
Jul 4, 2017

Conversation

mgiuca
Copy link
Collaborator

@mgiuca mgiuca commented Jul 3, 2017

This makes sharing the empty dictionary, or a dictionary with only unrecognised fields, a programmer error, and is designed to aid in future extensions (since if new fields are added, it will be a TypeError to exclusively use them without feature detection).

Also adds an appendix discussing extending the spec in the future.

Closes #48.


Preview | Diff

mgiuca added 2 commits July 3, 2017 14:49
This makes sharing the empty dictionary, or a dictionary with only
unrecognised fields, a programmer error, and is designed to aid in
future extensions (since if new fields are added, it will be a TypeError
to exclusively use them without feature detection).

Closes w3c#48.
@mgiuca
Copy link
Collaborator Author

mgiuca commented Jul 3, 2017

@sammc ptal.

Web platform tests updated here: web-platform-tests/wpt@master...mgiuca:web-share-errors-and-arguments

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.

2 participants