Skip to content
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

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

Merged
merged 4 commits into from Mar 20, 2018

Conversation

2 participants
@pjeby
Copy link
Contributor

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.

pjeby and others added some commits Mar 18, 2018

@danielbachhuber
Copy link
Member

danielbachhuber left a comment

Thanks @pjeby !

@danielbachhuber danielbachhuber added this to the 1.3.0 milestone Mar 20, 2018

@danielbachhuber danielbachhuber merged commit 0730fae into wp-cli:master Mar 20, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details

pjeby added a commit to pjeby/entity-command that referenced this pull request Aug 23, 2018

Support double-serialized options in option list
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
You can’t perform that action at this time.