-
Notifications
You must be signed in to change notification settings - Fork 349
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
Conflict grpc package name and message name #2176
Comments
Hi @alicialics and thank you for the report and the reproduction! Sorry but I'm not adding a lot here but just labeling it according to our new Contribution Guide and issue flow. It seems already got into Now in order to advance to If you have questions about how to create a failing test, we are available for any help around that and you can contact us here or directly (and also we have video tutorials on the link above). Thank you and sorry that this comment is not a complete solution (yet). |
See #2177 (comment) |
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Describe the bug
When the package name matches one of the grpc message we get an error
the error may be fixed in one of the two ways:
Change
message FOO {
to something else, like Foo or FAAChange
GetFOOsResponse
to something else, likeGetFoosResponse
orGetFAAsResponse
Change package name from
foo
to something elseSimilar to #1719
To Reproduce
Code sandbox: https://codesandbox.io/s/vigorous-shtern-8stbo
Expected behavior
no error when running yarn mesh
Environment:
The text was updated successfully, but these errors were encountered: