Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

implement CLI option to map proto imports to their module in the project. #495

Open
james-lawrence opened this issue Mar 1, 2023 · 1 comment

Comments

@james-lawrence
Copy link

currently imports of other proto files assumes the same relative path. if that assumption doesn't hold there doesn't seem to be a way to remap the path for the dependency.

see related: stephenh/ts-proto#596

@yibo-long
Copy link

yibo-long commented Jun 2, 2023

+1, it will be great for the support.

We manage our protos with different languages with dependencies. For example there is proto NPM package @spanio/a and proto NPM package @spanio/b with b depending on a as:

syntax = "proto3";
package io.span.b;

import "io/span/a/foo.proto";

message Bar {
  io.span.a.Foo foo = 1;
}

some option support like Mio/span/a/foo.proto=@spanio/a will be great! Maybe not prefered by everyone, but Mio/span/a=@spanio/a could make our lives much easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants