feat: allow proto_library as js_library#dep - #2721
Conversation
Design: - user expected to register a toolchain providing their protoc plugin for gen-es - Adapt ProtoInfo to JsInfo so a proto_library target can appear anywhere a js_library does Example of use currently in aspect-build/rules_ts#894
| @@ -0,0 +1,3 @@ | |||
| package(default_visibility = ["//visibility:public"]) | |||
|
|
|||
| toolchain_type(name = "protoc_plugin") | |||
There was a problem hiding this comment.
@dzbarsky should we drop this in contrib_toolchains ?
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5210cdb3d7
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
If this is the direction other rulesets such as ruby then I definitely think we should do the same. It might be nice to land this for the v3 release, which I thought was basically ready to go until seeing this... |
dzbarsky
left a comment
There was a problem hiding this comment.
github changed how comments work, i keep forgetting to submit now...




Design:
ProtoInfotoJsInfo, so a proto_library target can appear anywhere a js_library doesjs_proto_librarytargets to pollute the package where the proto_library appearsExample of use currently in aspect-build/rules_ts#894
TODO: