Define `null` as an invalid value for attributes and declare attempts to set `null` as undefined behavior (#992)
This commit is contained in:
parent
a15b95dafa
commit
906beb96fc
|
|
@ -25,10 +25,10 @@ Attributes SHOULD preserve the order in which they're set.
|
||||||
|
|
||||||
Attribute values expressing a numerical value of zero, an empty string, or an
|
Attribute values expressing a numerical value of zero, an empty string, or an
|
||||||
empty array are considered meaningful and MUST be stored and passed on to
|
empty array are considered meaningful and MUST be stored and passed on to
|
||||||
processors / exporters. Attribute values of `null` are considered to be not set
|
processors / exporters.
|
||||||
and get discarded as if that `Attribute` has never been created.
|
|
||||||
As an exception to this, if overwriting of values is supported, this results in
|
Attribute values of `null` are not valid and attempting to set a `null` value is
|
||||||
removing the attribute.
|
undefined behavior.
|
||||||
|
|
||||||
`null` values within arrays MUST be preserved as-is (i.e., passed on to span
|
`null` values within arrays MUST be preserved as-is (i.e., passed on to span
|
||||||
processors / exporters as `null`). If exporters do not support exporting `null`
|
processors / exporters as `null`). If exporters do not support exporting `null`
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue