-
Notifications
You must be signed in to change notification settings - Fork 5
Add a Gutenberg image-block insertion regression fixture #41
Copy link
Copy link
Open
Labels
area: media-libraryWordPress media upload and image-placement workflowWordPress media upload and image-placement workflowarea: wordpress-gutenbergWordPress REST API, Gutenberg input, and block placementWordPress REST API, Gutenberg input, and block placementcontribution: no-claimIndependent first contribution; open a PR without claimingIndependent first contribution; open a PR without claiminggood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is needed
Description
Activity
Metadata
Metadata
Assignees
Labels
area: media-libraryWordPress media upload and image-placement workflowWordPress media upload and image-placement workflowarea: wordpress-gutenbergWordPress REST API, Gutenberg input, and block placementWordPress REST API, Gutenberg input, and block placementcontribution: no-claimIndependent first contribution; open a PR without claimingIndependent first contribution; open a PR without claiminggood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is needed
Problem
The painful editor workflow is not only finding an image; it is placing the image in the correct Gutenberg section without duplicating blocks or disturbing existing content.
Pictovap has WordPress/Gutenberg placement logic. A focused fixture would make this behavior easier for a new contributor to understand and safer to change.
Scope
Add one regression fixture and one test for inserting a Gutenberg image block into existing post content.
A good PR should:
Acceptance criteria
make contributor-smokeandmake contribution-checkpass.Contributor path
This is
contribution: no-claim: fork the repo and open a PR directly. No reservation comment is needed.