woocommerce

History

Matt Sherman 2b12908a80 Add @woocommerce/create-product-editor-block package (#38263 ) * Initial commit for create-product-editor-block * Changelog * Add stylelint support * Install WooCommerce and WooCommerce Beta Tester in wp-env * Set PHP and WordPress versions * Enable product block editor after wp-env setup * Lower priority for modifying template, so that the template is actual there! * Update wp-env afterSetup command to use npx * Update output README.md * Update README for package * Use long form of template parm name in README * Remove unused example in block config * Update block registration to handle both WP 6.2 and WP 6.3 * Include note about how to change version of WP and WC in README * Update WP to 6.2.1 * Remove explicit enqueuing of block script and style * Update minimum required versions of WordPress and PHP in generated plugin file * Enable feature flag option after setup of wp-env * Add minimum required WC version to generated plugin file * Support wp-env lifecycleScripts * Guard against product_block_editor not enabled or missing template * Update lock file		2023-05-26 08:16:57 -04:00
..
$slug.php.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
.editorconfig.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
.eslintrc.js.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
.gitignore.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
.prettierrc.json.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
.stylelintrc.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
.wp-env.override.json.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
README.md.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
composer.json.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
readme.txt.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
tsconfig.json.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00
webpack.config.js.mustache	Add @woocommerce/create-product-editor-block package (#38263 )	2023-05-26 08:16:57 -04:00

readme.txt.mustache

=== {{title}} ===
{{#author}}
Contributors:      {{author}}
{{/author}}
Tags:              block
Tested up to:      6.1
Stable tag:        {{version}}
{{#license}}
License:           {{license}}
{{/license}}
{{#licenseURI}}
License URI:       {{{licenseURI}}}
{{/licenseURI}}

{{description}}

== Description ==

This is the long description. No limit, and you can use Markdown (as well as in the following sections).

For backwards compatibility, if this section is missing, the full length of the short description will be used, and
Markdown parsed.

== Installation ==

This section describes how to install the plugin and get it working.

e.g.

1. Upload the plugin files to the `/wp-content/plugins/{{slug}}` directory, or install the plugin through the WordPress plugins screen directly.
1. Activate the plugin through the 'Plugins' screen in WordPress


== Frequently Asked Questions ==

= A question that someone might have =

An answer to that question.

= What about foo bar? =

Answer to foo bar dilemma.

== Screenshots ==

1. This screen shot description corresponds to screenshot-1.(png|jpg|jpeg|gif). Note that the screenshot is taken from
the /assets directory or the directory that contains the stable readme.txt (tags or trunk). Screenshots in the /assets
directory take precedence. For example, `/assets/screenshot-1.png` would win over `/tags/4.3/screenshot-1.png`
(or jpg, jpeg, gif).
2. This is the second screen shot

== Changelog ==

= {{version}} =
* Release

== Arbitrary section ==

You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated
plugins where more information needs to be conveyed that doesn't fit into the categories of "description" or
"installation." Arbitrary sections will be shown below the built-in sections outlined above.