You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Invalid Type Declarations for PhoneCall class
For
PhoneCall
objects, thecontact
property is declared to be Not Nullable. However in types.js, thecontact
property on thePhoneCall
instance is not validated or set when the constructor'scontact
parameter is nullish.Similarly, the
callAttributes
field forPhoneCall
objects is declared to be Not Nullable. In the constructor forPhoneCall
, thecallAttributes
property is set without checking or validating this parameter, meaning thatPhoneCall.callAttributes
can potentially benull
orundefined
.The type declarations for
PhoneCall
in types.d.ts should be revised to either require non-null input to thecontact
andcallAttributes
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.The text was updated successfully, but these errors were encountered: