You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently the CLI command config:set changes all integer values to string values when saving changes, regardless whether these values were changed or not.
Values which seem to be boolean because they have content "true" or "false" are saved as booleans, but that is not really safe.
The CLI should save configuration in the same way as the administrator does, so the data types of the particular values are determined by the administrator/components/com_config/forms/application.xml file or by the existing configuration.php file.
Is your feature request related to a problem? Please describe.
Currently the CLI command
config:set
changes all integer values to string values when saving changes, regardless whether these values were changed or not.Values which seem to be boolean because they have content "true" or "false" are saved as booleans, but that is not really safe.
See the comment here: #42618 (comment) .
Describe the solution you'd like
The CLI should save configuration in the same way as the administrator does, so the data types of the particular values are determined by the
administrator/components/com_config/forms/application.xml
file or by the existingconfiguration.php
file.The should not be a data type conversion based on the content of a value like it is currently done for boolean here https://github.com/joomla/joomla-cms/blob/5.0-dev/libraries/src/Console/SetConfigurationCommand.php#L445-L450 .
Additional context
See also issue #42612 and PR #42618 .
The text was updated successfully, but these errors were encountered: