-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
Mismatched types #398
Comments
I'm seeing something similar with the TS types. I'm making a Paste of the method declaration in 5.0.9 from my /**
* Creates or updates a user.
* @param {object} user - The user details.
* @returns {Promise<User>} The created or updated user's details.
* @async
* @see {@link https://developer.zendesk.com/api-reference/ticketing/users/users/#create-or-update-user}
* @example
* const user = await client.users.createOrUpdate({name: 'John Doe', email: 'john@example.com'});
*/
createOrUpdate(user: object): Promise<User>; And the original JS declaration in the repo: node-zendesk/src/clients/core/users.js Lines 190 to 201 in ac07d2c
Paste of the actual resolved value: {
response: {
json: [Function: json],
status: 201,
headers: { get: [Function: get] },
statusText: 'Created'
},
result: {
id: ...,
... other User properties ...
}
} |
I have the same issue with |
I just contributed to the bounty on this issue. Each contribution to this bounty has an expiry time and will be auto-refunded to the contributor if the issue is not solved before then. To make this a public bounty or have a reward split, the maintainer can reply to this comment. |
ditto — exactly what @mackstann is seeing returned is also returning for me when using |
any update on this? |
having the same issue with |
Having similar issue with In the documentation it suggests; |
Describe the Bug
Types are not matching actual values returned
Example Code
Expected Behavior
Either
.id
reported as type error or following output:Actual Behavior
Either
.resource
reported as type error and following output:Environment Information
node-zendesk
version: 5.0.7The text was updated successfully, but these errors were encountered: