Support protobuf extend keyword when in kImportEs6 mode
#8
Conversation
This file contains 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
davemasselink
commented
Jun 30, 2023
gonzojive
approved these changes
Jul 6, 2023
reddaly
pushed a commit
to gonzojive/rules_ts_proto
that referenced
this pull request
Jul 7, 2023
Add a test case for exercising ES6 generation of proto files using the `extend` keyword. Builds on work in `protobuf-javascript` repo: [PR#8](gonzojive/protobuf-javascript#8).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Enable interpretable compilation of protos which use the
extendkeyword into JS (most pressingly, the longrunning -> http -> annotations dependency chain).Testing of this is being done in
rules_ts_protorepo: PR#9