Partial alternative attempt at allowEmptyValue clarification #3803
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[EDIT: Closed in favor of #3812]
Alternative to:
allowEmptyValue: false
#3792This attempts to clarify based on objections to the previous attempt to clarify. However, it is incomplete as the concept of "empty value" is not well-defined, which is why the following is embedded in the PR text and (obviously) not intended to be merged:
TODO: What values are empty? RFC6570 defines
null
,[]
,{}
, and objects with onlynull
properties (e.g.{"foo": null, "bar": null}
to be "undefined" and serialize as empty values, but it does not consider the empty string to be undefined even though it also serializes as an empty value. Also, how does this interact withcontent
, which is not RFC6570-based and may result in empty values through any number of different circumstances.