-
Notifications
You must be signed in to change notification settings - Fork 43
feat: support gRPC and http apis #41
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
Conversation
* Change package name for generated code from proto * Move protos to root folder * Add logger * Refactor routes
d09894a to
467b5a8
Compare
| MaxRecvMsgSizeInMB int `default:"10"` | ||
| MaxSendMsgSizeInMB int `default:"10"` |
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 was wondering what if we just set it really big value and forget about it? I see very little value in making this configurable, to be honest?
| var Logger *zap.Logger | ||
|
|
||
| func init() { | ||
| l, err := zap.NewProduction() |
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 have not used zap so correct me if I am wrong, don't we need to initialize it with config level? Or don't we have configurable log levels like debug/warn/etc?
Also, any specific reason we are creating a package level logger object?
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.
Ya just wanted basic logger. Later will integrate with config object to control log levels.
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.
We will move to the salt logger soon.
Uh oh!
There was an error while loading. Please reload this page.