10ea0b9f10da7dc9880fc9ad663605e2f6175b38

Committed 23 Apr 2024 11:30AM UTC coverage: 52.248% (+0.003%) from 52.245%

Build # 10ea0b9f10da7dc9880fc9ad663605e2f6175b38

Build Type

Pull #21329

github

Committed by

enricobattocchi

Commit Message

Require copy-webpack-plugin explicitly

Pull Request Pull Request #21329: Convert the How To block and the FAQ block to the Blocks V3 API

Run Details

7551 of 13901 branches covered (54.32%)

Branch coverage included in aggregate %.

0 of 13 new or added lines in 3 files covered. (0.0%)

78 existing lines in 2 files now uncovered.

28618 of 55324 relevant lines covered (51.73%)

40602.86 hits per line

Source File
Press 'n' to go to next uncovered line, 'b' for previous

0.0

/packages/js/src/structured-data-blocks/how-to/block.js

/* External dependencies */
import { registerBlockType } from "@wordpress/blocks";

/* Internal dependencies */
import block from "./block.json";
import HowTo from "./components/HowTo";
import legacy from "./legacy";

registerBlockType( block, {
        /**
         * The edit function describes the structure of your block in the context of the editor.
         * This represents what the editor will render when the block is used.
         *
         * The "edit" property must be a valid function.
         *
         * @link https://wordpress.org/gutenberg/handbook/block-api/block-edit-save/
         * @returns {Component} The editor component.
         */
        edit: ( { attributes, setAttributes, className } ) => {
                // Because setAttributes is quite slow right after a block has been added we fake having a single step.
                if ( ! attributes.steps || attributes.steps.length === 0 ) {
                        attributes.steps = [ { id: HowTo.generateId( "how-to-step" ), name: [], text: [] } ];
                }

                return <HowTo { ...{ attributes, setAttributes, className } } />;
        },

        /* eslint-disable react/display-name */
        /**
         * The save function defines the way in which the different attributes should be combined
         * into the final markup, which is then serialized by Gutenberg into post_content.
         *
         * The "save" property must be specified and must be a valid function.
         *
         * @link https://wordpress.org/gutenberg/handbook/block-api/block-edit-save/
         * @returns {Component} The display component.
         */
        save: function( { attributes } ) {
                return <HowTo.Content { ...attributes } />;
        },
        /* eslint-enable react/display-name */

        deprecated: [
                {
                        attributes: block.attributes,
                        save: legacy.v11_4,
                },
                {
                        attributes: block.attributes,
                        save: legacy.v8_2,
                },
        ],
} );

1	/* External dependencies */
2	import { registerBlockType } from "@wordpress/blocks";
3
4	/* Internal dependencies */
5	import block from "./block.json";
6	import HowTo from "./components/HowTo";
7	import legacy from "./legacy";
8
NEW 9	registerBlockType( block, {	×
10	/**
11	* The edit function describes the structure of your block in the context of the editor.
12	* This represents what the editor will render when the block is used.
13	*
14	* The "edit" property must be a valid function.
15	*
16	* @link https://wordpress.org/gutenberg/handbook/block-api/block-edit-save/
17	* @returns {Component} The editor component.
18	*/
19	edit: ( { attributes, setAttributes, className } ) => {
20	// Because setAttributes is quite slow right after a block has been added we fake having a single step.
NEW 21	if ( ! attributes.steps \|\| attributes.steps.length === 0 ) {	×
NEW 22	attributes.steps = [ { id: HowTo.generateId( "how-to-step" ), name: [], text: [] } ];	×
23	}
24
NEW 25	return <HowTo { ...{ attributes, setAttributes, className } } />;	×
26	},
27
28	/* eslint-disable react/display-name */
29	/**
30	* The save function defines the way in which the different attributes should be combined
31	* into the final markup, which is then serialized by Gutenberg into post_content.
32	*
33	* The "save" property must be specified and must be a valid function.
34	*
35	* @link https://wordpress.org/gutenberg/handbook/block-api/block-edit-save/
36	* @returns {Component} The display component.
37	*/
38	save: function( { attributes } ) {
NEW 39	return <HowTo.Content { ...attributes } />;	×
40	},
41	/* eslint-enable react/display-name */
42
43	deprecated: [
44	{
45	attributes: block.attributes,
46	save: legacy.v11_4,
47	},
48	{
49	attributes: block.attributes,
50	save: legacy.v8_2,
51	},
52	],
53	} );

Yoast / wordpress-seo / 10ea0b9f10da7dc9880fc9ad663605e2f6175b38

Source File Press 'n' to go to next uncovered line, 'b' for previous

Source File
Press 'n' to go to next uncovered line, 'b' for previous