-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect Typescript types on MessageInstance #606
Comments
This issue has been added to our internal backlog to be prioritized. Pull requests and +1s on the issue summary will help it move up the backlog. |
@eshanholtz is there a source of truth one can use as a reference for the Message Resource schema? It would help anyone looking to create a PR or have a temporary work around for the type discrepancies. |
The source of truth is internal (and only has |
UPDATE: fixed this by deleting my
relating to
Downgrading from Deploying functions to a Probably worth noting that |
Couple more mistyped fields on
|
10 months open now folks. Additionally, |
+1 |
+1 |
not fixed yet |
Issue Summary
The
MessageInstance
class looks as if it contains incorrect types for some of its instance properties. Properties such aserrorCode
anderrorMessage
can be nullable according to the documentation so I would think that the type oferrorCode
should benumber | null
rather than simplynumber
as it currently is.Props types that seem incorrect:
errorCode
: should benumber | null
rather thannumber
errorMessage
: should bestring | null
rather thanstring
price
: should bestring | null
rather thanstring
priceUnit
: should bestring | null
rather thanstring
messagingServiceSid
: should bestring | null
rather thanstring
(From the docs: "The SID of the Messaging Service used with the message. The value is null if a Messaging Service was not used.")Code Snippet
Compare the type of the instance property
errorCode
hereto the sample JSON response in the documentation:
Exception/Log
Technical details:
v3.49.0
12.8.3
The text was updated successfully, but these errors were encountered: