-
Notifications
You must be signed in to change notification settings - Fork 73
Support strict output format #1004
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
base: trunk
Are you sure you want to change the base?
Conversation
143b2dd
to
73aeacc
Compare
73aeacc
to
e47009d
Compare
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @singerb. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Why a separate flag and not something like Should we perhaps just fix the existing |
/** | ||
* @Then /^STDOUT should be valid JSON$/ | ||
*/ | ||
public function stdout_should_be_valid_json() { | ||
$output = $this->result->stdout; | ||
|
||
json_decode( $output ); | ||
|
||
if ( JSON_ERROR_NONE !== json_last_error() ) { | ||
throw new Exception( 'STDOUT is not valid JSON: ' . json_last_error_msg() ); | ||
} | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
That sounds like a good idea.
That would be a major breaking change I believe. I dont want to break which is already working :-) |
dc5681e
to
98a3b49
Compare
Fixes #748
--format