-
Notifications
You must be signed in to change notification settings - Fork 773
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
Make client args credentials
and options
optional
#512
Conversation
Currently the TypeScript generated clients require that `null` be passed to `credentials` and `options` if they're not being used. It's easier to simply make those arguments optional. I've left the `null` portion of the type though to maintain backwards compatibility.
Not sure why Kokoro still hasn't completed its checks... but otherwise this PR is ready for review. |
Yea I have to apply the tag for the kokoro test to run, and the reason I haven't applied the tag is because I thought we did this and reverted a long while ago and I forgot the reason now and I haven't got a chance to dig out the history. I might remember wrong. Will get to this asap. |
Gotcha. Thanks @stanley-cheung , no rush. |
@stanley-cheung I looked through the history of the master branch and found no evidence that those args were ever optional, outside of having been looser types in the past (i.e. |
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. This is only for the typescript and commonjs+dts output. Thanks for the contributions.
Currently the TypeScript generated clients require that
null
be passed tocredentials
andoptions
if they're not being used. It's easier to simply make those arguments optional. I've left thenull
portion of the type though to maintain backwards compatibility.