Address viewport placeholder review feedback

[roborourke]

Summary

Follow-up to the merged #27, addressing @kadamwhite's post-merge review of the viewport-placeholder code. Two changes, no behavior change.

Changes

Rules of hooks (review comment)

withViewportPlaceholder called useState / useSelect / useEffect after the HOC's early return for non-core/query blocks — a rules-of-hooks violation (it worked in practice only because name is stable per block instance). Everything after the early return is now extracted into a LazyBlockEdit component whose hooks run unconditionally, so the HOC reduces to:

createHigherOrderComponent( ( BlockEdit ) => {
	return ( props ) => {
		if ( props.name !== 'core/query' ) {
			return <BlockEdit { ...props } />;
		}

		return <LazyBlockEdit BlockEdit={ BlockEdit } { ...props } />;
	};
}, 'withViewportPlaceholder' );

Trim the doc block (review comment)

Applied KAdam's suggested tighter wording for the QueryLoopPlaceholder doc block, which conveys the same information more directly.

Testing

• npm run build — compiles cleanly.
• npm run lint:js — clean.
• The existing tests/e2e/viewport-placeholder.spec.js coverage is unchanged, since behavior is identical.

🤖 Generated with Claude Code

---

Generated by Claude Code

[github-actions]

Playwright test results

 22 passed

Details

 22 tests across 7 suites
 1 minute, 20 seconds
 e0a0fe5

[svandragt]

Interesting to think if that's possible for all blocks loading lazily.

[roborourke]

Potentially. Are there other blocks that are heavy on requests you can think of?