Skip to content

Add --unserialize flag to 'option list' command#156

Merged
danielbachhuber merged 4 commits intowp-cli:masterfrom
pjeby:unserialize
Mar 20, 2018
Merged

Add --unserialize flag to 'option list' command#156
danielbachhuber merged 4 commits intowp-cli:masterfrom
pjeby:unserialize

Conversation

@pjeby
Copy link
Copy Markdown
Contributor

@pjeby pjeby commented Mar 18, 2018

While option get unserializes values, option list does not, making the value data less useful. This PR adds an --unserialize flag that unserializes the values, making the outputs more useful for e.g. diffing complex object values.

Copy link
Copy Markdown
Member

@danielbachhuber danielbachhuber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @pjeby !

@danielbachhuber danielbachhuber added this to the 1.3.0 milestone Mar 20, 2018
@danielbachhuber danielbachhuber added command:option Related to 'option' command command:option-list Related to 'option list' command labels Mar 20, 2018
@danielbachhuber danielbachhuber merged commit 0730fae into wp-cli:master Mar 20, 2018
pjeby added a commit to pjeby/entity-command that referenced this pull request Aug 23, 2018
Some plugins (e.g. awesome-support) and frameworks (e.g. titan-framework) double-serialize their options.  This PR updates my previous PR (wp-cli#156, implementing `--unserialize`) to handle the case where options are double-serialized in this fashion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

command:option Related to 'option' command command:option-list Related to 'option list' command

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants