-
Notifications
You must be signed in to change notification settings - Fork 75
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
Check usage of Kernel::System::SysConfig::SettingUpdate #561
Comments
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
bschmalhofer
added a commit
that referenced
this issue
Oct 22, 2020
Checked the usage. Fixed some cases where the status was not checked correctly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The module
Kernel::System::SysConfig
is an outlier, in that it return a hash instead of a scalar value. This means that in list context a list of key value pairs is returned. In scalar context the number of entries in the result hash is returned.Checking for success should be done via the attribute
$Result{Success}
. But at least inKernel::Modules::MigrateFromOTRS
there is a call toSettingUpdate
in scalar context.TODO:
Kernel::System::SysConfig::SettingUpdate()
Kernel::System::SysConfig::SettingUpdate()
The text was updated successfully, but these errors were encountered: