We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I have a .proto file that contains messages that I would like to use in multiple services:
.proto
message
$ cat shared.proto syntax = "proto3"; package shared; message SharedRequest { string In = 1; }
And if truss is run on this file, I propose that truss generates a corresponding .pb.go file.
truss
.pb.go
In the case of shared.proto the generated shared.pb.go would look like this.
shared.proto
shared.pb.go
Currently, truss panics because it cannot find the service name. (This used to have a nice error, guess this needs to have a test as well)
$ truss shared.proto panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x64568f]
To implement:
Service
Service.Name
cmd/truss/main.go
parseInput()
parsesvcname.FromPaths
execprotoc.GeneratePBDotGo()
This is a step to fix #241
The text was updated successfully, but these errors were encountered:
Fixed by #246.
Thanks again @eriktate and welcome to being a contributor!
Sorry, something went wrong.
No branches or pull requests
If I have a
.proto
file that containsmessage
s that I would like to use in multiple services:And if
truss
is run on this file, I propose that truss generates a corresponding.pb.go
file.In the case of
shared.proto
the generatedshared.pb.go
would look like this.Currently, truss panics because it cannot find the service name. (This used to have a nice error, guess this needs to have a test as well)
To implement:
Service
orService.Name
cmd/truss/main.go
, functionparseInput()
needs toparsesvcname.FromPaths
.pb.go
files will be generatedexecprotoc.GeneratePBDotGo()
to actually generate the .pb.go files.This is a step to fix #241
The text was updated successfully, but these errors were encountered: