feat: re-add kitchensink proto with recursive type coverage - #12
Open
shaileshpadave wants to merge 1 commit into
Open
feat: re-add kitchensink proto with recursive type coverage#12shaileshpadave wants to merge 1 commit into
shaileshpadave wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Re-adds kitchensink.proto after the revert in #11. The Status enum shadowing issue that caused the revert is fixed — AuthInterceptor now has an explicit io.grpc.Status import.
Needed as a test target for the conductor-side StackOverflow fix (orkes-io/orkes-conductor#3912) which handles recursive proto types during gRPC discovery.