Skip to content

Conversation

@CyrusNajmabadi
Copy link
Contributor

@CyrusNajmabadi CyrusNajmabadi commented Jul 9, 2019

Fixes: #950

The latest release of grpc-node cannot be used in a typescript project that uses -noImplicitAny. This is due to a signature being added without a specified return type. This causes the return type to implicitly be 'any' which TS explicitly disallows. For projects that use strict flags to catch lots of bugs, this prevents usage of this version of grpc entirely.

Fix is simple, just actually provide an annotation for this method.

The latest release of grpc-node cannot be used in a typescript project that uses -noImplicitAny.  This is due to a signature being added without a specified return type.  This causes the return type to implicitly be 'any' which TS explicitly disallows.  For projects that use strict flags to catch lots of bugs, this prevents usage of this version of grpc entirely.
@thelinuxfoundation
Copy link

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.

After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

Regards,
CLA GitHub bot

@CyrusNajmabadi
Copy link
Contributor Author

This was introduced in #796. Tagging @murgatroid99 and @nicolasnoble for this regression. Thanks!

Copy link
Member

@murgatroid99 murgatroid99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this.

@CyrusNajmabadi
Copy link
Contributor Author

Happy to help!

@murgatroid99 murgatroid99 merged commit 93b1a2f into grpc:master Jul 9, 2019
@CyrusNajmabadi
Copy link
Contributor Author

Thanks all!

@CyrusNajmabadi CyrusNajmabadi deleted the patch-1 branch July 9, 2019 23:32
@CapOM
Copy link
Contributor

CapOM commented Jul 10, 2019

Hi, thx for this patch, has it been back ported to 1.22.x branch yet ?

@CapOM
Copy link
Contributor

CapOM commented Jul 10, 2019

Well in case not, I submitted a PR #959

@lock lock bot locked as resolved and limited conversation to collaborators Oct 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Latest releast breaks -noImplicitAny typescript builds.

5 participants