Add behat test for config has after concatenation assignment

[pwtyler]

Summary

• Adds a behat scenario to config-has.feature that verifies wp config has finds variables and constants when the wp-config.php contains a variable assignment with string concatenation (e.g. $x = 'foo' . $bar;)

Depends on wp-cli/wp-config-transformer#64

Dependency note

wp-cli/wp-config-transformer#64 is now merged. composer.json temporarily points at dev-main via a VCS repository entry so CI runs against the fixed code. Once a release of wp-config-transformer is cut, this PR will be updated to pin to that version and the repositories override removed.

[github-actions]

Hello! 👋

Thanks for opening this pull request! Please check out our contributing guidelines. We appreciate you taking the initiative to contribute to this project.

Contributing isn't limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation.

Here are some useful Composer commands to get you started:

• composer install: Install dependencies.
• composer test: Run the full test suite.
• composer phpcs: Check for code style violations.
• composer phpcbf: Automatically fix code style violations.
• composer phpunit: Run unit tests.
• composer behat: Run behavior-driven tests.

To run a single Behat test, you can use the following command:

# Run all tests in a single file
composer behat features/some-feature.feature

# Run only a specific scenario (where 123 is the line number of the "Scenario:" title)
composer behat features/some-feature.feature:123

You can find a list of all available Behat steps in our handbook.

[gemini-code-assist]

Code Review

This pull request introduces a new test scenario to verify that the wp config has command correctly identifies variables and constants when they follow a concatenation assignment. A review comment points out that the wp-config.php content in the test is missing the required <?php opening tag, which is necessary for the PHP parser to correctly process the file and for the test to function as intended.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

Adds coverage to ensure wp config has can detect constants/variables in wp-config.php even when assignments include concatenation and other multi-line/complex expressions, and temporarily updates dependency resolution to include the upstream fix.

Changes:

• Added a new Behat Scenario Outline in config-has.feature to cover concatenation, multiline strings, and multiline define() values.
• Updated composer.json to pull wp-cli/wp-config-transformer from dev-main via a VCS repository override (pending a tagged release).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
features/config-has.feature	Adds a scenario outline to validate wp config has detection across complex wp-config expressions.
composer.json	Temporarily points wp-cli/wp-config-transformer to dev-main using a VCS repository for CI coverage of the upstream fix.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Requiring wp-cli/wp-config-transformer as dev-main (combined with the VCS repository override above) makes installs non-deterministic and can break CI unexpectedly as main moves. Consider pinning to a specific commit hash or a tagged pre-release version for reproducibility, and then switching back to a stable semver constraint once a release is cut.

Suggested change

	"wp-cli/wp-config-transformer": "dev-main"
	"wp-cli/wp-config-transformer": "dev-main#<full-commit-hash>"