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
runPHPWithOptions step in the example doesn't match with the heading #1374
Comments
adamziel
added a commit
that referenced
this issue
May 9, 2024
Changing the headings for each step at https://wordpress.github.io/wordpress-playground/blueprints-api/steps to correspond with the real value of the step property in the blueprint The `ActivatePluginStep` heading becomes `activatePlugin`, `CpStep` becomes `cp` and so on. Closes #1375 Closes #1374 cc @juanmaguitar
Merged
adamziel
added a commit
that referenced
this issue
May 9, 2024
Changing the headings for each step at https://wordpress.github.io/wordpress-playground/blueprints-api/steps to correspond with the real value of the step property in the blueprint The `ActivatePluginStep` heading becomes `activatePlugin`, `CpStep` becomes `cp` and so on. Closes #1375 Closes #1374 cc @juanmaguitar
@adamziel I think the example at runPHPWithOptions still needs to be updated to reflect the right step name
|
Aha, correct |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The step runPHPWithOptions example doesn't match the step stated in the heading.
The example of
runPHPWithOptions
is:Should it be instead?
The text was updated successfully, but these errors were encountered: