Mention "testsPort" .wp-env.json setting#49388
Conversation
* The `.wp-env.json` also supports setting `testsPort` for the test port, in addition to `env.tests.port`. * This file appears to now support more than six options
|
👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @enderandpeter! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other. If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information. |
|
Congratulations on your first merged pull request, @enderandpeter! We'd like to credit you for your contribution in the post announcing the next WordPress release, but we can't find a WordPress.org profile associated with your GitHub account. When you have a moment, visit the following URL and click "link your GitHub account" under "GitHub Username" to link your accounts: https://profiles.wordpress.org/me/profile/edit/ And if you don't have a WordPress.org account, you can create one on this page: https://login.wordpress.org/register Kudos! |
|
Thanks! |
What?
Mentions the
testsPortoption for.wp-env.jsonin the table that lists this file's options, consistent with this page referring to the option further down. Also, more than six options appear to be supported, so that wording was changed.Why?
Provides more clarity on how to use this tool. Creating an
envsection is an available choice, but settingtestsPortis more straightforward for when you just want to change that and create a new wp-env that does not interfere with another.How?
This PR will simply make mention of
testsPortsimilarly to how other options are summarized.Testing Instructions
wp-envenvironment, but settestsPortport in the.wp-env.jsonto a value other than8889.wp-envtest instance is using the specified port.Testing Instructions for Keyboard
N/A
Screenshots or screencast