-
Notifications
You must be signed in to change notification settings - Fork 5
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
Adapt to use new service widget #49
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.
Please, update the yast2 dependency.
src/modules/FtpServer.rb
Outdated
# for backward compatibility, see {#write_daemon}. When the service | ||
# is configured by using the UI, it directly saves the service, see | ||
# {Yast2::SystemService#save}. | ||
def save_status |
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.
In the http-sever
I used save_service
for an identical method. What do you about use the same naming, when possible, for the "service widget adaptation"?
I don't mind to change save_service
to save_status
if you think it is more accurate :)
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.
Well, in this case I named it #save_status
because it saves the service status in different ways depending on the mode. It does not always "save the service", understanding "service" is our SystemService.
Part of PBI https://trello.com/c/uAe4i9Ru/107-5-fate319428-allow-socket-activation-widget