-
Notifications
You must be signed in to change notification settings - Fork 45
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
Improve visor config and startup/shutdown logic. #360
Improve visor config and startup/shutdown logic. #360
Conversation
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.
Really huge improvement. Just some minor queries here and there
if !ok { | ||
return ErrAppNotFound | ||
} | ||
if args != nil { |
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 should be checking len(args) != 0
imo here. Just to exclude non-nil but still empty args
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.
@Darkren But what if people want to run an app with no args?
* Separated app-associated functionality within /pkg/visor into /pkg/app/launcher. * Added the concept of visor.BaseConfig() to simplify obtaining default values. * Made startup/shutdown logic modular and introduced init and shutdown stacks. * Shutdown now uses module-based timeouts and wait groups.
47b6fb0
to
912fe09
Compare
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.
Really great improvements! Good job!
Fixes #339 fixes #173 fixes #170
Changes:
/pkg/visor
into/pkg/app/launcher
.visor.BaseConfig()
to simplify obtaining default values.