-
Notifications
You must be signed in to change notification settings - Fork 19
Imports in protobuf #257
Comments
You are right, our first iteration just ignored them. The reason is that it's not easy to track where in the filesystem or in the web you can find each import. If you have references, I am happy to give it a go in the next weeks (we also accept PRs, of course!). |
I think it is sufficient to only look for the files in filesystem. There is no standard place to look, the For reference, the language guide does a decent job of explaining this. I don't know if I will get any time to make a PR for this, I am just hacking around on the weekends for now, so I wouldn't make any promises 😄 |
I am getting this error on a gRPC definition with imports. Calls without imports work. Is it correct to think this error is a manifestation of the import limitation?
|
Hey! @rossabaker seems related, we are currently discussing how to solve this and will likely come up with a fix soon, thanks!! 🙌🏻 |
Thanks, @kutyel! I ran into this on the googleapis, if you're looking for a good real-world example. We're enjoying the library very much, and I'll be more than happy to test. |
Just ran into something like this as well. One of the methods by which this is handled in the proto-lens library is through using extra-src-files in the package.yaml/cabal file. Perhaps the TH could get at that info and just iterate through the .proto files? |
Does this error related to this issue?
I have to work around this by expending TemplateHaskell splice to:
And then add a |
It seems they are not supported. The template haskell code just ignores them (except for
google.protobuf.Empty
).The text was updated successfully, but these errors were encountered: