-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
protoc-gen-swagger: check typeIndex when typeName is Method #833
Conversation
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Hi @hexfusion, thanks a bunch for the contribution! Any chance you could add some new test casee for this to prevent future regressions? Thanks! |
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
It seems the generator changes caused a diff in one of the generated files. Is that expected? If so, you'll need to rerun the generator (see CONTRIBUTING.md). |
@johanbrandhorst looking at the source of the proto I believe the change is expected, will update. |
Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
Looks great, thanks! |
/cc @gyuho |
@johanbrandhorst just curious about general time-frame when we might expect this to be released. Thanks! |
A new release you mean? We don't currently have a set release schedule, I can see if we're waiting for anything in particular but I might just release 1.6.4 tomorrow. |
that would be fantastic, and greatly appreciated. |
FYI @hexfusion I will be backing out these changes, it seems they caused #923, please see #924. Please feel free to open another PR reverting the revert where we can add some more tests to ensure we get the best of both worlds. |
This reverts the changes introduced in grpc-ecosystem#833. It caused a regression in the swagger generator allow_merge behaviour. Fixes grpc-ecosystem#923
isProtoPathMatches() doesn't return false if svcIdx != methIdx when typeName == Method. The results in comments belonging to other services polluting swagger spec. We noticed this regression when using protoc 3.5.1+, although I still can't say why it started.
Fixes: #746