Clarify allowEmptyValue further #3798
Conversation
handrews
added
clarification
Make it clear that the default value does not do anything, and the non-default value (true) changes the normal expected behavior of the "schema" or "content" fields. This also explains why the keyword is safe to deprecate, as "schema" and "content" can be used to allow empty values in a more typical way.
|
I think this PR is now ready for review. |
|
@ralfhandl Everyone is encouraged to review/approve this and other draft PRs. But with this much confusion on what is supposed to happen, I want to make sure that we do not merge it yet. See policy issue #3802 which I filed because at least 3 different people have merged PRs that I thought needed more attention, but we don't have any well-defined way to express that (discussions in TDC calls and comments in the PRs did not work). |
| @@ -1044,7 +1044,7 @@ Field Name | Type | Description | |||
| <a name="parameterDescription"></a>description | `string` | A brief description of the parameter. This could contain examples of use. [CommonMark syntax](https://spec.commonmark.org/) MAY be used for rich text representation. | |||
| <a name="parameterRequired"></a>required | `boolean` | Determines whether this parameter is mandatory. If the [parameter location](#parameterIn) is `"path"`, this property is **REQUIRED** and its value MUST be `true`. Otherwise, the property MAY be included and its default value is `false`. | |||
| <a name="parameterDeprecated"></a> deprecated | `boolean` | Specifies that a parameter is deprecated and SHOULD be transitioned out of usage. Default value is `false`. | |||
| <a name="parameterAllowEmptyValue"></a> allowEmptyValue | `boolean` | Sets the ability to pass empty-valued parameters. This is valid only for `query` parameters and allows sending a parameter with an empty value. Default value is `false`. If [`style`](#parameterStyle) is used, and if behavior is `n/a` (cannot be serialized), the value of `allowEmptyValue` SHALL be ignored. Use of this property is NOT RECOMMENDED, as it is likely to be removed in a later revision. | |||
| <a name="parameterAllowEmptyValue"></a> allowEmptyValue | `boolean` | If `true`, allows passing empty-valued parameters regardless of `schema` or `content`. This is valid only for `query` parameters. Default value is `false`. If [`style`](#parameterStyle) is used, and if behavior is `n/a` (cannot be serialized), the value of `allowEmptyValue` SHALL be ignored. Use of this property is NOT RECOMMENDED, as it is likely to be removed in a later revision; instead, ensure that the parameter's schema accepts any desired empty value(s). | |||
There was a problem hiding this comment.
Are ?foo and ?foo= both considered to have empty values? Should we say anything about whether one or the other is correct or preferred?
There was a problem hiding this comment.
I'd say both have empty values because if I run both variants through the standard URL parser of my current favorite programming language or build a service with my favorite web app framework both forms result in
{ 'foo' => '' }so my server-side code would not be able to spot the difference.
Which of course is only my very personal opinion 😄
There was a problem hiding this comment.
@mikekistler it's not possible to produce ?foo (without an =). This is unfortunate, but it was discussed extensively in issue #1573 (the previous attempt to sort this out).
There was a problem hiding this comment.
it's not possible to produce
?foo(without an=)
Just did with
http.get("http://localhost:3000/?foo", ...My minimalistic server tells me that it received the URL /?foo. No = anywhere.
[EDIT: Closed in favor of #3812]
[EDIT: See #3803 for an alternative based on discussion below.]
allowEmptyValue: false#3792Make it clear that the default value does not do anything, and the non-default value (true) changes the normal expected behavior of the "schema" or "content" fields. This also explains why the keyword is safe to deprecate, as "schema" and "content" can be used to allow empty values in a more typical way.