refactor(ai-assistant): use backend provided followup questions - #722
Merged
davids-ensemble merged 8 commits intoAug 17, 2026
Merged
Conversation
|
Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
|
❌ Test ResultsStatus: Some tests failed! 🔍 Click to view failed testsTest Coverage ReportOverall Coverage Summary
Coverage by File/Directory
Coverage report generated at 2026-08-11T15:48:53.134Z |
❌ Test ResultsStatus: Some tests failed! 🔍 Click to view failed testsTest Coverage ReportOverall Coverage Summary
Coverage by File/Directory
Coverage report generated at 2026-08-14T10:22:26.839Z |
Hoist scrollToBottom to module scope with a `force` option so the user-initiated scrolls (sendMessage, restoreChatHistory) and the streaming scrolls (onContent, onCitation, finalizeAnswer) share one helper. Route onError through showFallbackSuggestions and make showSuggestedQuestions idempotent so onComplete can safely re-reveal follow-ups when the backend omits answerComplete. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The 600ms setTimeout was a leftover from the static-suggestions design, where follow-ups were only revealed after the full answer streamed. With dynamic follow-ups revealed idempotently from onAnswerComplete/onComplete, the delay served no purpose. Reveal them synchronously instead. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Revert the stop button to send, clear the a11y busy indicator, and announce the reply as soon as the answer text is done (onAnswerComplete) instead of waiting for the terminal complete event, which fires only after follow-up questions generate. Removes the confusing window where the stop button lingered over an already-finished answer. A run-once endResponding() handles the teardown at whichever terminal event fires first, so aborted/partial streams (no answerComplete) are still covered and the reply is announced exactly once. finalizeAnswer calls it, since a finalized answer always means responding is over; the stopped-by-user path calls it standalone without finalizing the bubble. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
davids-ensemble
force-pushed
the
feat-ai-assistant-fq-changes
branch
from
August 14, 2026 10:25
66fc748 to
2991f6e
Compare
❌ Test ResultsStatus: Some tests failed! 🔍 Click to view failed testsTest Coverage ReportOverall Coverage Summary
Coverage by File/Directory
Coverage report generated at 2026-08-14T10:26:31.868Z |
❌ Test ResultsStatus: Some tests failed! 🔍 Click to view failed testsTest Coverage ReportOverall Coverage Summary
Coverage by File/Directory
Coverage report generated at 2026-08-14T10:26:36.544Z |
SavithaSAngadi
approved these changes
Aug 17, 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
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.
JIRA: ADPGENAI-226