You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to improve support for Bazel, we should introduce a rule to allow generation of TS protos idiomatically with Bazel.
The benefits
Ability to synchronise generated code for multiple targets
Native experience for Bazel users
Contribution to the ecosystem of Bazel
How
A ts_proto_library already exists (docs) leverages Protobuf.JS. We can utilize the learnings from there to add a similar rule.
The code should be contributed to rules_typescript for uniformity but we should test against the rule ourselves on our CI.
Notes
Initial research of this shows this should be very doable and can provide better integration with Bazel than Protobuf.JS as we can choose to compile individual protos based on the dependency analysis from Bazel.
If you have a use case for ts-protoc-gen and Bazel, please let us know so we can better cater for it.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
In order to improve support for Bazel, we should introduce a rule to allow generation of TS protos idiomatically with Bazel.
The benefits
How
A ts_proto_library already exists (docs) leverages Protobuf.JS. We can utilize the learnings from there to add a similar rule.
The code should be contributed to rules_typescript for uniformity but we should test against the rule ourselves on our CI.
Notes
Initial research of this shows this should be very doable and can provide better integration with Bazel than Protobuf.JS as we can choose to compile individual protos based on the dependency analysis from Bazel.
If you have a use case for ts-protoc-gen and Bazel, please let us know so we can better cater for it.
The text was updated successfully, but these errors were encountered: