feat(feed): bouton de régénération du résumé IA dans la popin - #54
Merged
Conversation
Le résumé LinkedIn d'un article est mis en cache en Firestore — quand il
est de mauvaise qualité, il n'existait aucun moyen d'en générer un nouveau.
- Backend : POST /articles/{id}/summary accepte ?force=true qui ignore le
cache article_summaries et régénère (le nouveau résumé écrase l'ancien).
- Frontend : bouton 🔄 dans l'en-tête de la popin SummaryLayer ; il relance
handleSummarize en mode forcé (popin fermée, toast de progression, popin
rouverte avec le nouveau résumé).
- Tests : le flux SSE restitue le cache sans force et l'ignore avec force.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FWZSW8k5gSphqLMou41kJF
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FWZSW8k5gSphqLMou41kJF
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.
Le résumé LinkedIn d'un article est mis en cache en Firestore — quand il
est de mauvaise qualité, il n'existait aucun moyen d'en générer un nouveau.
cache article_summaries et régénère (le nouveau résumé écrase l'ancien).
handleSummarize en mode forcé (popin fermée, toast de progression, popin
rouverte avec le nouveau résumé).
Co-Authored-By: Claude Fable 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01FWZSW8k5gSphqLMou41kJF