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
#64 : Remove -l flag, move all configuration to yaml, a lot of refact… #65
Conversation
@@ -10,73 +10,20 @@ import ( | |||
"github.com/commitdev/commit0/internal/templator" | |||
) | |||
|
|||
func TestGenerateJenkins(t *testing.T) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess these cases are covered by the integration tests now anyway, plus the logic inside of the CI generator is much simpler now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI stuff looks good. I'm glad I wrote those tests to make sure.
internal/generate/proto/generate.go
Outdated
} | ||
|
||
func GenerateProtoServiceLibs(config *config.Commit0Config) { | ||
idlRoot := fmt.Sprintf("%s-idl", config.Name) | ||
func GenerateProtoServiceLibs(service config.Service) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Before the idl repo produced would be a single repo that contained all the service idls & generated code split by folders, mainly for sharing protos (such as health) and for ease of use - is the intention to change this to multiple repos?
mkdir -p gen/{{ $language }} | ||
protoc ${PROTO_SOURCES} --{{ $language }}_out=plugins=grpc,paths=source_relative:proto ./proto/health/*.proto | ||
{{- range .Services}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Related to the comment above, if this is removed how are the the service proto generation commands produced?
generate-http: | ||
mkdir -p gen/go | ||
protoc ${PROTO_SOURCES} --grpc-gateway_out=logtostderr=true,paths=source_relative:proto --swagger_out=logtostderr=true:proto ./proto/health/*.proto | ||
{{- range .Services}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question for above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few questions about proto servuce generation
…oring
Mostly done, but I feel like the proto stuff might still need some love.