Skip to content

Redefine allowEmptyValue #611

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

Closed
webron opened this issue Mar 27, 2016 · 2 comments
Closed

Redefine allowEmptyValue #611

webron opened this issue Mar 27, 2016 · 2 comments

Comments

@webron
Copy link
Member

webron commented Mar 27, 2016

Currently the spec provides allowEmptyValue which is valid for query or formData parameters.

When sending query parameters, they can have no value (acting as a flag) or a an empty value. That is ?foo&bar or ?foo=&bar= respectively. Current spec doesn't allow specifying the difference

This issue is derived from #81.

Parent: #565.

@fehguy
Copy link
Contributor

fehguy commented Feb 1, 2017

@webron I think this has been handled in the 3.0 draft. Can you please confirm?

@webron
Copy link
Member Author

webron commented Mar 3, 2017

Yes, it's indirectly explained (depends on style).

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

No branches or pull requests

2 participants