block nesting deep: block_depth

Open
#6,126 16 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
php, wordpress
Domain
frontend, tooling

Research direction

The finding editability/block_nesting_deep records a block_depth of 13 and 16 against a threshold of 10, so start by locating where that depth metric is computed and where the nesting check is defined in the static-site-importer tooling. Then read the acceptance gate at tools/import-loop/gates/accept.mjs (revision 10b332f1) to see what a whole re-import must satisfy. Done means a whole re-import of the capture lowers this finding's count without new blockers or visual parity regressions; there is no reduced page to iterate on, so expect slow feedback.

Written by the indexing model from the issue text.

Description

Finding

editability/block_nesting_deep on block_depth, seen in 2 cell(s) of an imported site:

route width evidence
/about/ 1440 {"depth":13,"threshold":10}
/ 1440 {"depth":16,"threshold":10}

Acceptance

This is a whole-site check: it measures the imported site, so there is no reduced page. A fix is accepted when a whole re-import of the capture with the change lowers this finding's occurrence count, with no other blocker appearing or growing and no visual parity regression on any route or width. The import loop's acceptance gate measures exactly that (static-site-importer tools/import-loop/gates/accept.mjs, at 10b332f1).

Loop signature: 62c5ece57f35


AI disclosure: filed by the static-site import findings loop (Homeboy workflow on the Lab). The finding, reduction, and body are generated by deterministic scripts; Claude (Anthropic) wrote those scripts with Chris Huber.

Dominant language
PHP
Stars
28
Forks
5
Avg merge
2h 59m
Merged PRs (30d)
942

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Automattic/blocks-engine

All issues in Automattic/blocks-engine

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.