Right now, neither the CustomData nodes nor the Custom event properties are particularly authoritative, and the only way to fully remove them is to unset both. This PR makes the CustomData node authoritative, and will overwrite and unset properties on ParseCustom(). Going the other way would be much harder, because JSONNodes would need to be Removed and non-events don't yet have Custom properties.
Implementation note: the ternary is necessary because of JSONLazyCreator, if there was a
Right now, neither the CustomData nodes nor the Custom event properties are particularly authoritative, and the only way to fully remove them is to unset both. This PR makes the CustomData node authoritative, and will overwrite and unset properties on ParseCustom(). Going the other way would be much harder, because JSONNodes would need to be
Removed and non-events don't yet have Custom properties.Implementation note: the ternary is necessary because of JSONLazyCreator, if there was a
this could look like
force push was for commit signing, don't worry about it