Reason: the API currently has a mix of null and undefined. To unify this, we will use undefined everywhere. This works better than null since undefined is the "default" in JavaScript, for example with optional chainging, missing properties, empty array slots, function argument defaults. Also: null is a valid JSON value, so for the Content.json type we must use undefined when there is no JSON.
This is a breaking change in the following properties and methods:
selection
onChange (contentErrors and patchResult properties)
Reason: the API currently has a mix of
null
andundefined
. To unify this, we will useundefined
everywhere. This works better thannull
sinceundefined
is the "default" in JavaScript, for example with optional chainging, missing properties, empty array slots, function argument defaults. Also:null
is a valid JSON value, so for theContent.json
type we must useundefined
when there is no JSON.This is a breaking change in the following properties and methods:
selection
onChange
(contentErrors
andpatchResult
properties)onRenderContextMenu
(selection
property)onSelect
validate
(returnsundefined
)select