[MWPW-195871] Fix: Speaker image update and delete not reflecting in table#158
Merged
Conversation
After saving a new image the table showed the stale photo because handleFormSubmit called apiService directly, bypassing cachedApi and its cache-invalidation logic. Removing an image also had no effect because no DELETE was ever sent to ESP. - Use cachedApi.updateSpeaker/createSpeaker so the series cache is invalidated before loadSpeakers re-fetches - Track removedImageId in SpeakerFormDialog and pass it to the parent; handleFormSubmit now calls deleteSpeakerImage when a saved image is removed Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
qiyundai
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves: https://jira.corp.adobe.com/browse/MWPW-195871
After saving a new image the table showed the stale photo because handleFormSubmit called apiService directly, bypassing cachedApi and its cache-invalidation logic. Removing an image also had no effect because no DELETE was ever sent to ESP.