Using custom import during codegen for re-exported crates

[jeremija]

Hello, currently code that's generated using prost-validate-build always ends up hardcoding ::prost-validate. This makes it tricky to build a code-generating tool on top of it and re-export prost-validate, so the users can only worry about specifying a single crate in the dependencies.

Would you be open to a PR that adds a method such as prost_validate_path for using a re-exported prost-validate crate?

For example, this is how it can be configured in prost-build: https://docs.rs/prost-build/latest/prost_build/struct.Config.html#method.prost_path

[Adphi]

Hello @jeremija,

Thanks for opening this issue.
That seems like a useful addition.

Feel free to submit a PR, and let me know if you need any help!

[jeremija]

Great, I'll try to come up with something soon. Thanks for a quick response!

[jeremija]

I finally started looking into this. Do you know where are the super::super::google::protobuf::* references coming from? For example https://github.com/linka-cloud/prost-validate//blob/49b5be36df98d4af5ff3b8c6a0fed0b509c53ba1/prost-validate-derive-core/src/wkt.rs#L56

[Adphi]

These are the well-known types, but I'm afraid I don't remember why there's a "super::super" prefix.