Excerpt Generation: Synchronize generating state across inline and modal buttons - #908
Conversation
…tatus across multiple instances
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #908 +/- ##
==========================================
Coverage 80.43% 80.43%
Complexity 2565 2565
==========================================
Files 110 110
Lines 10448 10448
==========================================
Hits 8404 8404
Misses 2044 2044
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
What?
Consolidates the excerpt generation status across the inline and modal excerpt generation buttons so that both UI elements reflect the generating state simultaneously.
Why?
Previously, the inline button and modal/panel button each maintained independent
isGeneratinglocal component states. If a user clicked the inline button and then opened the modal, the modal button remained enabled, allowing parallel duplicate API generation requests to be triggered. Now, when generation is active from either button, both buttons are disabled and show loading state.Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Sonnet 4.6
Used for: Validating bug, suggesting a fix.
Testing Instructions
Screencast
Before
Screen.Recording.2026-07-30.at.3.28.42.PM.mov
After
Screen.Recording.2026-07-30.at.3.25.32.PM.mov
Changelog Entry