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

Fix import path behaviour when using full path #78

Closed

Conversation

johanbrandhorst
Copy link

@johanbrandhorst johanbrandhorst commented Jun 8, 2020

This change makes protoc-gen-star conform to the behaviour of protoc-gen-go in the presence of an import_path parameter that contains slashes.

See https://github.com/golang/protobuf/blob/v1.4.2/protoc-gen-go/generator/generator.go#L637-L643
for evidence of this behaviour in protoc-gen-go.

Fixes #77

@rodaine
Copy link
Contributor

rodaine commented Aug 5, 2020

Can we make this as an additive test (without modifying any of the existing ones)? The tests listed here were meant to catch regressions in the handling of the go_package and plugin param interactions. The package one there specifically was catching reserved keywords as well.

This change makes protoc-gen-star conform to the behaviour
of protoc-gen-go in the presence of an import_path
parameter that contains slashes.

See https://github.com/golang/protobuf/blob/v1.4.2/protoc-gen-go/generator/generator.go#L637-L643
for evidence of this behaviour in protoc-gen-go.

Fixes lyft#77
@johanbrandhorst
Copy link
Author

Can we make this as an additive test (without modifying any of the existing ones)? The tests listed here were meant to catch regressions in the handling of the go_package and plugin param interactions. The package one there specifically was catching reserved keywords as well.

Done

@pdecks
Copy link
Contributor

pdecks commented Dec 21, 2023

Closing this since it is obsolete given we migrated to protobuf APIv2, which deprecated import_path. See protocolbuffers/protobuf-go@3e80249

@pdecks pdecks closed this Dec 21, 2023
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

Successfully merging this pull request may close these issues.

Incorrect handling of import_path when it is a path
3 participants