We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe your use case and the problem you are facing
Running wp config list or wp config get, boolean values are shown as 1 / empty string.
wp config list
wp config get
$ wp config list name value type ... WP_DEBUG 1 constant WP_DEBUG_LOG 1 constant WP_DEBUG_DISPLAY constant
$ wp config get WP_DEBUG_DISPLAY
Describe the solution you'd like
Instead of echoing directly the boolean value, resulting in 1 / nothing, boolean values should be considered strictly and shown as true / false, i.e.
$ wp config list name value type ... WP_DEBUG true constant WP_DEBUG_LOG true constant WP_DEBUG_DISPLAY false constant
$ wp config get WP_DEBUG_DISPLAY false
In this way we could understand better if we set really a false value or an empty string instead.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Feature Request
Describe your use case and the problem you are facing
Running
wp config list
orwp config get
, boolean values are shown as 1 / empty string.Describe the solution you'd like
Instead of echoing directly the boolean value, resulting in 1 / nothing, boolean values should be considered strictly and shown as true / false, i.e.
In this way we could understand better if we set really a false value or an empty string instead.
The text was updated successfully, but these errors were encountered: