Invalid Type Declarations for PhoneCall class
For PhoneCall objects, the contact property is declared to be Not Nullable. However in types.js, the contact property on the PhoneCall instance is not validated or set when the constructor's contact parameter is nullish.
Similarly, the callAttributes field for PhoneCall objects is declared to be Not Nullable. In the constructor for PhoneCall, the callAttributes property is set without checking or validating this parameter, meaning that PhoneCall.callAttributes can potentially be null or undefined.
The type declarations for PhoneCall in types.d.ts should be revised to either require non-null input to the contact and callAttributes parameters of the constructor, or to indicate these properties as nullable. This issue could also be present in other structures defined in the types.d.ts file as well.
Invalid Type Declarations for PhoneCall class
For
PhoneCallobjects, thecontactproperty is declared to be Not Nullable. However in types.js, thecontactproperty on thePhoneCallinstance is not validated or set when the constructor'scontactparameter is nullish.Similarly, the
callAttributesfield forPhoneCallobjects is declared to be Not Nullable. In the constructor forPhoneCall, thecallAttributesproperty is set without checking or validating this parameter, meaning thatPhoneCall.callAttributescan potentially benullorundefined.The type declarations for
PhoneCallin types.d.ts should be revised to either require non-null input to thecontactandcallAttributesparameters of the constructor, or to indicate these properties as nullable. This issue could also be present in other structures defined in the types.d.ts file as well.