The current protocol allows non-required properties to have null/undefined value for all non-required properties whereas lisk-transactions throws an error in case, say if a property value is null it was expected to be string.
Actual behavior
The validate step for transaction throws an error if a property is null or undefined.
Which version(s) does this affect? (Environment, OS, etc...)
Expected behavior
The current protocol allows non-required properties to have null/undefined value for all non-required properties whereas lisk-transactions throws an error in case, say if a property value is
nullit was expected to bestring.Actual behavior
The
validatestep for transaction throws an error if a property isnullorundefined.Which version(s) does this affect? (Environment, OS, etc...)
release/2.1.0