Enhance Content Summary block detection to nested blocks by Intenzi · Pull Request #810 · WordPress/ai

Intenzi · 2026-07-01T09:41:28Z

What?

Closes #809

Enhances the Content Summarization experiment to detect Content Summary block inside nested-level blocks.

Why?

It solves the problem of new Content Summary block insertion when we want to regenerate the content summary if existing one is moved inside a nested block level such as inside a Group/Column block.
This PR ensures that the existing Content Summary block is found and edited instead.

How?

The fix is performed by implementing a recursive function named findSummaryBlock.

Recursively performs Depth First Search to identify the Content Summary block's existence.

This function replaces the existing search logic for the Content Summary block.

Implemented E2E test validating the same.

Additionally fixed a performance issue of the useSelect hook re-evaluating and running on every single render due to missing dependancy array. This was fixed by adding [] as empty dependancy array.

Use of AI Tools

AI assistance: Yes
Tool(s): Antigravity IDE
Model(s): Gemini 3.5 Flash (Low)
Used for: Identifying relevant code file, deciding on implementation for enhancement. E2E test was implemented via it. The performance fix was detected by the model. Final implementation and tests were reviewed and edited by me.

Testing Instructions

Enable Content Summarization Experiment.
Create a new post with minimum required content for the button to enable.
Click the Generate Summary button present inside the Post sidebar.
Create a Group/Column block and place the generated Content Summary group block inside it.
Identify that the button still states Regenerate Summary - (inside both Post sidebar and selected Block hovering menu bar)
Click Regenerate Summary.
Identify that the existing Content Summary group block has been modified instead of inserting a new block.

Screenshots or screencast

Visual Cues:

Manual Testing Video (from the step of Regenerate Summary click):

Enhancement.Complete.-.Content.Summarization.mov

Changelog Entry

Changed - Content Summary block detection from top-level only to checking nested blocks as well.

…tion

…mmarization exp

github-actions · 2026-07-01T09:41:40Z

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Intenzi <intenzi@git.wordpress.org>
Co-authored-by: yogeshbhutkar <yogeshbhutkar@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

codecov · 2026-07-01T09:47:11Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.50%. Comparing base (30fc728) to head (3309fa2).

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #810   +/-   ##
==========================================
  Coverage      75.50%   75.50%           
  Complexity      2086     2086           
==========================================
  Files             99       99           
  Lines           8626     8626           
==========================================
  Hits            6513     6513           
  Misses          2113     2113

Flag	Coverage Δ
unit	`75.50% <ø> (ø)`

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Intenzi · 2026-07-01T11:40:23Z

Raised #811 to increase gh action run timeout which was causing the E2E test job to cancel mid-run.

yogeshbhutkar · 2026-07-01T11:46:30Z

-				block.name === 'core/group' &&
-				block.attributes[ 'aiGeneratedSummary' ] === true // eslint-disable-line dot-notation
-		);
+		const summaryGroup = findSummaryBlock( allBlocks );


We could instead use flattenBlocks here.

Ref:

ai/src/utils/blocks.ts

Lines 91 to 101 in 203cb1d

export function flattenBlocks< T extends BlockWithContent >(

blocks: T[]

): T[] {

return blocks.reduce< T[] >( ( acc, block ) => {

acc.push( block );

if ( block.innerBlocks?.length ) {

acc.push( ...flattenBlocks( block.innerBlocks as T[] ) );

}

return acc;

}, [] );

}

… Content Summary block

yogeshbhutkar · 2026-07-01T13:43:29Z

+ * @param {any[]} blocks List of blocks to search.
+ * @return {any|null} The found block or null.
+ */
+function findSummaryBlock( blocks: any[] ): any {


I believe we could narrow the types further.

Suggested change

function findSummaryBlock( blocks: any[] ): any {

import type { Block } from '@wordpress/blocks';

function findSummaryBlock( blocks: Block[] ): Block | undefined

yogeshbhutkar · 2026-07-01T13:43:34Z

+		flattenBlocks( blocks ).find(
+			( block ) =>
+				'core/group' === block.name &&
+				true === block.attributes[ 'aiGeneratedSummary' ] // eslint-disable-line dot-notation


Yoda-style comparison is technically (IMO) unnecessary in JS/TS-World. I believe we should keep this consistent with other segments of the JS/TS codebase.

Yes that makes sense, I'll align the coding style to the codebase and follow the same.

yogeshbhutkar · 2026-07-01T13:52:58Z

+		// Wait for the generation to complete (button changes from "Generating..." back to "Regenerate Summary").
+		await expect(
+			page.getByRole( 'button', {
+				name: 'Generating…',
+				exact: true,
+			} )
+		).not.toBeVisible();


This negative assertion can pass even if the UI never reaches that state.

I have refactored the logic to now wait on the Content Summary block's content to change after button click. Thus I have now removed that assertion.

yogeshbhutkar · 2026-07-06T06:05:02Z

+		// Create a new post containing a nested summary block inside columns, with enough content.
+		const nestedContent =
+			// Content
+			'<!-- wp:paragraph -->' +


Nit: We could use editor.insertBlock with innerBlocks here. This should make it easy to accomodate in case the block metadata/markup contract changes upstream in the future.

Intenzi added 3 commits June 30, 2026 14:07

perf: optimize useSelect performance in useSummaryGeneration hook

1d76c40

feat: recursively search for nested summary block in useSummaryGenera…

53d2f0d

…tion

test: add E2E test for nested block summary regneration in content-su…

203cb1d

…mmarization exp

Intenzi changed the title ~~Feat/summarization nested regeneration~~ Enhance Content Summary block detection to nested blocks Jul 1, 2026

Intenzi mentioned this pull request Jul 1, 2026

Enhancement/Fix: Content Summarization block to be found inside nested blocks #809

Open

Intenzi mentioned this pull request Jul 1, 2026

Increase gh actions runner timeout for E2E tests completion #811

Merged

yogeshbhutkar suggested changes Jul 1, 2026

View reviewed changes

refactor: findSummaryBlock to use flattenBlocks utility for searching…

ecac53c

… Content Summary block

Intenzi requested a review from yogeshbhutkar July 1, 2026 13:24

yogeshbhutkar suggested changes Jul 1, 2026

View reviewed changes

dkotter assigned Intenzi Jul 1, 2026

Intenzi added 4 commits July 1, 2026 21:45

refactor: narrow type annotations in findSummaryBlock method

dbe11d1

refactor: remove yoda conditions to align coding style

10fc7fb

test: improve assertions in nested content summarization e2e test

a87e36e

Merge branch 'develop' into feat/summarization-nested-regeneration

facc22d

Intenzi requested a review from a team July 1, 2026 16:36

yogeshbhutkar reviewed Jul 6, 2026

View reviewed changes

yogeshbhutkar approved these changes Jul 6, 2026

View reviewed changes

Intenzi added 2 commits July 7, 2026 10:59

test: use editor.insertBlock for nested content summary block insertion

2afc77e

Merge branch 'develop' into feat/summarization-nested-regeneration

3309fa2

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Enhance Content Summary block detection to nested blocks#810

Enhance Content Summary block detection to nested blocks#810
Intenzi wants to merge 10 commits into
WordPress:developfrom
Intenzi:feat/summarization-nested-regeneration

Intenzi commented Jul 1, 2026 •

edited by github-actions Bot

Loading

Uh oh!

github-actions Bot commented Jul 1, 2026 •

edited

Loading

Uh oh!

codecov Bot commented Jul 1, 2026 •

edited

Loading

Uh oh!

Intenzi commented Jul 1, 2026

Uh oh!

yogeshbhutkar Jul 1, 2026

Uh oh!

yogeshbhutkar Jul 1, 2026

Uh oh!

yogeshbhutkar Jul 1, 2026

Uh oh!

Intenzi Jul 1, 2026

Uh oh!

yogeshbhutkar Jul 1, 2026

Uh oh!

Intenzi Jul 1, 2026

Uh oh!

yogeshbhutkar Jul 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	export function flattenBlocks< T extends BlockWithContent >(
	blocks: T[]
	): T[] {
	return blocks.reduce< T[] >( ( acc, block ) => {
	acc.push( block );
	if ( block.innerBlocks?.length ) {
	acc.push( ...flattenBlocks( block.innerBlocks as T[] ) );
	}
	return acc;
	}, [] );
	}

	function findSummaryBlock( blocks: any[] ): any {
	import type { Block } from '@wordpress/blocks';
	function findSummaryBlock( blocks: Block[] ): Block \| undefined

Uh oh!

Conversation

Intenzi commented Jul 1, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What?

Why?

How?

Use of AI Tools

Testing Instructions

Screenshots or screencast

Changelog Entry

Uh oh!

github-actions Bot commented Jul 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov Bot commented Jul 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Intenzi commented Jul 1, 2026

Uh oh!

yogeshbhutkar Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

yogeshbhutkar Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

yogeshbhutkar Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

Intenzi Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

yogeshbhutkar Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

Intenzi Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

yogeshbhutkar Jul 6, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Intenzi commented Jul 1, 2026 •

edited by github-actions Bot

Loading

github-actions Bot commented Jul 1, 2026 •

edited

Loading

codecov Bot commented Jul 1, 2026 •

edited

Loading