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
Currently, ts_proto_library produces files for the direct proto dep it is passed. This is unideal since it forces users to both vendor in all transitive proto libraries they need typescript support for, and also manually link together a tree of ts_proto_library and js_libraries which mirrors the exact structure of the proto dependencies themselves
Describe the feature
Ideally, ts_proto_library would run an aspect over all transitive dependencies such that only one ts_proto_library target needs to be authored by the user. The write_source_files implementation would likely need to be rethought out for third party proto dependencies at that point
The text was updated successfully, but these errors were encountered:
What is the current behavior?
Currently, ts_proto_library produces files for the direct proto dep it is passed. This is unideal since it forces users to both vendor in all transitive proto libraries they need typescript support for, and also manually link together a tree of ts_proto_library and js_libraries which mirrors the exact structure of the proto dependencies themselves
Describe the feature
Ideally, ts_proto_library would run an aspect over all transitive dependencies such that only one
ts_proto_library
target needs to be authored by the user. Thewrite_source_files
implementation would likely need to be rethought out for third party proto dependencies at that pointThe text was updated successfully, but these errors were encountered: