-
Notifications
You must be signed in to change notification settings - Fork 80
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
feat: imports API endpoints #884
Conversation
Size Change: +1.98 kB (0%) Total Size: 285 kB
|
src/client.ts
Outdated
* @private | ||
* @param {{ limit?: number; offset?: number }} options pagination options | ||
* | ||
* @return {APIResponse} An ImportTask |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should have a specific response type for this method and for the others as well, right?
Is import_task: {}
accurate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅ added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this isn't exactly true since it's a richer version of it
maybe we should define listResponse, getResponse etc. How is it done in other endpoints?
Add types for Import API endpoints Update src/client.ts Update src/client.ts Update src/client.ts Update src/types.ts Co-Authored-By: Peter Deme <[email protected]>
lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
CLA
Description of the changes, What, Why and How?
Changelog