-
Notifications
You must be signed in to change notification settings - Fork 31
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: add runs()
and builds()
top level endpoints
#468
Conversation
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.
Thanks for pushing this forward.
It looks good, can you please add unit tests for new methods?
You can check here for example to have idea how to do it.
// builds() { | ||
// return new BuildCollectionClient(this._options()); | ||
// } | ||
builds(): BuildCollectionClient { |
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.
Please add a reference to API docs into comments, the same as we had in the rest of the endpoints.
// runs() { | ||
// return new RunCollectionClient(this._options()); | ||
// } | ||
runs(): RunCollectionClient { |
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.
Same as the build list, please add a reference to docs.
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.
👍
FYI I did some dependency updates including the shared eslint config, which now enforces import order, that's the reason for the conflicts. Those problems are autofixable. |
I'd like to ship new minor version, would be good to include this there, @foxt451 can you please rebase and fix the linting issues? |
017bf26
to
e41dbe7
Compare
runs()
and builds()
top level endpoints
Closes #296