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
It would be great if we could simply add a line to buf.gen.yaml that made the generator add a prefix to the generated types' names. For example, I would just say typesPrefix: "Pb" in the yaml file, and then for this proto enum:
enum Foo {
...
}
the generated TS code would be
export enum PbFoo {
...
}
Same for message types and their TS classes. The motivation for this request is to avoid name collisions between generated TS types and manually-written types that correspond to them. Without this feature I have to manually alias names when I import them, as in
import {Foo as PbFoo} from ...
The text was updated successfully, but these errors were encountered:
This would be quite useful to have. In our case we're generating wrapper classes that provide an API similar to v1 and protobuf-js, and having the base types prefixed would be handy.
It would be great if we could simply add a line to
buf.gen.yaml
that made the generator add a prefix to the generated types' names. For example, I would just saytypesPrefix: "Pb"
in the yaml file, and then for this proto enum:the generated TS code would be
Same for message types and their TS classes. The motivation for this request is to avoid name collisions between generated TS types and manually-written types that correspond to them. Without this feature I have to manually alias names when I import them, as in
The text was updated successfully, but these errors were encountered: