[gogenproto] Allow specifying a Go package mapping for import paths #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
→ It may be the case that you're importing protos that are generated in some other way than with
gogenproto
but which similarly have a conventional Go path mapping (e.g. they don't specifygo_package
but instead get automatic package names. Unfortunately right now that means you can't depend on these protos from yourgogenproto
-using protos, since you can't tellgogenproto
what their package name will be.Changes
=
and the Go package prefix, you can use conventional (directory based) path mapping.Testing