ce1a6acbc25bc240bac5264e23262d4059521a7d

Committed 28 May 2024 08:22AM UTC coverage: 52.735% (-0.04%) from 52.77%

Build # ce1a6acbc25bc240bac5264e23262d4059521a7d

Build Type

push

github

Committed by

vraja-pro

Commit Message

Merge remote-tracking branch 'origin/trunk' into feature/decouple-hidden-fields

Run Details

7359 of 13368 branches covered (55.05%)

Branch coverage included in aggregate %.

5 of 67 new or added lines in 10 files covered. (7.46%)

2 existing lines in 2 files now uncovered.

28302 of 54255 relevant lines covered (52.16%)

41401.53 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 { useBlockProps } from "@wordpress/block-editor";
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 } ) => {
                const blockProps = useBlockProps();

                // 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 <div { ...blockProps }>
                        <HowTo { ...{ attributes, setAttributes, className } } />
                </div>;
        },

        /**
         * 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: ( { attributes } ) => {
                const blockProps = useBlockProps.save( attributes );

                return <HowTo.Content { ...blockProps } />;
        },

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

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

Yoast / wordpress-seo / ce1a6acbc25bc240bac5264e23262d4059521a7d

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