We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Providing (additional) yml support for blueprint definition would greatly improve the usability of blueprints.
yml supports:
comments for explaining why a blueprint step is required (or what it does) and what it does
multiline values (for writeFile)
{ "step": "writeFile", "path": "/wordpress/wp-content/mu-plugins/rewrite.php", "data": "<?php /* Use pretty permalinks */ add_action( 'after_setup_theme', function() { global $wp_rewrite; $wp_rewrite->set_permalink_structure('/%postname%/'); $wp_rewrite->flush_rules(); } );" }
This multiline data could be written in yml in true multiline fashion which is much more readable
references (see example here : https://x.com/LarsGersmann/status/1684156867440771075) can also improve readability
the blueprint jsonschema can be even applied to yaml for validation/autocompletion (at least vscode supports this)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Providing (additional) yml support for blueprint definition would greatly improve the usability of blueprints.
yml supports:
comments for explaining why a blueprint step is required (or what it does) and what it does
multiline values (for writeFile)
This multiline data could be written in yml in true multiline fashion which is much more readable
references (see example here : https://x.com/LarsGersmann/status/1684156867440771075) can also improve readability
the blueprint jsonschema can be even applied to yaml for validation/autocompletion (at least vscode supports this)
The text was updated successfully, but these errors were encountered: