Refactor wp config create to set config values through WPConfigTransformer

[Copilot]

wp config create still had a separate value-writing path from the transformer-backed commands, which duplicated escaping/validation behavior and made new validation logic hard to centralize. This change makes create a thin wrapper: render defaults first, then apply requested values through wp-cli/wp-config-transformer.

• Create flow now routes value writes through transformer

  • Render wp-config.mustache with baseline defaults (including empty placeholders for salts when needed).
  • After file creation, apply user-provided DB/table-prefix values via WPConfigTransformer::update().
  • Apply generated salts via WPConfigTransformer::update() when salts are generated.
  • Keep fallback remote salts injection behavior intact when local generation fails.

• Removed create-specific escaping path

  • Deleted the legacy escape_config_value() path used only by create.
  • Value formatting/escaping behavior is now consistently handled by the transformer library for transformed entries.

• Focused feature coverage for transformer-path escaping

  • Added a config create feature scenario covering special-character handling for DB_CHARSET to ensure values written through the transformer are preserved and readable via wp config get.

$config_transformer->update(
	'constant',
	'DB_CHARSET',
	$assoc_args['dbcharset'],
	[ 'add' => true ]
);

[codecov]

Codecov Report

❌ Patch coverage is 92.07921% with 8 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/Config_Command.php	92.07%	8 Missing ⚠️

📢 Thoughts on this report? Let us know!

[Copilot]

Pull request overview

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