-
Notifications
You must be signed in to change notification settings - Fork 504
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
Support nginx conf #1130
Support nginx conf #1130
Conversation
Codecov ReportAttention: ❗ Your organization needs to install the Codecov GitHub app to enable full functionality.
... and 7 files with indirect coverage changes 📢 Thoughts on this report? Let us know! |
cmd/client/commandv2/common/spec.go
Outdated
@@ -0,0 +1,109 @@ | |||
/* |
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.
Can we use a more specific package name instead common
which is not suggested by any Golang guide.
Ref: https://dave.cheney.net/2019/01/08/avoid-package-names-like-base-util-or-common
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.
sure, let me update it!
type Options struct { | ||
NginxConf string | ||
Output string | ||
Prefix string |
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.
Prefix is too general? Can we use --resource-prefix
which is allowed to be empty.
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.
updated!
Co-authored-by: Yun Long <[email protected]>
Co-authored-by: Yun Long <[email protected]>
No description provided.