Add reply-data filter and generic suggestion rendering - #198
Merged
Conversation
- Redesign the frontend chat widget (header with avatar/name/status, modern bubbles, pill input, refined launcher, entrance animation). - Add a global "Chat Sound" toggle and a per-visitor mute control in the chat menu; remove the open/close click sound. - Add a "Message Timestamp" show/hide toggle. - Show the welcome message and suggested questions on first load of the inline chat block. - Inline the chat-button SVGs server-side (no runtime fetch / icon flash) and use a bundled SVG as the default icon instead of an emoji. - Keep the typing dots, suggestion chips, and menu legible on similar colors, and theme the menu from the chat colors. - Resolve outstanding PHPStan issues (gmdate guard, require_once ignore).
Reveal the assistant's reply progressively over Server-Sent Events, with a graceful fallback to the existing background + polling flow on hosts that buffer or cannot stream, so the bot keeps working everywhere. - Add a custom admin-ajax streaming endpoint (Stream) that proxies OpenAI's stream to the browser; the API key stays server-side. - Share a single prompt, JSON schema and response interpreter across the streaming and poll paths so replies never diverge by transport. - The widget tries streaming first and falls back to polling when no event arrives in time; the outcome is cached per browser and re-probed after 24h. - Decode the streamed `response` field incrementally via json_decode so escapes and surrogate-pair emoji render correctly while streaming. - Preserve existing contracts: moderation stays up front, hyve_chat_request and hyve_chat_response fire once per reply, analytics unaffected. Closes Codeinwp/hyve#183
- Redesign the frontend chat widget (header with avatar/name/status, modern bubbles, pill input, refined launcher, entrance animation). - Add a global "Chat Sound" toggle and a per-visitor mute control in the chat menu; remove the open/close click sound. - Add a "Message Timestamp" show/hide toggle. - Show the welcome message and suggested questions on first load of the inline chat block. - Inline the chat-button SVGs server-side (no runtime fetch / icon flash) and use a bundled SVG as the default icon instead of an emoji. - Keep the typing dots, suggestion chips, and menu legible on similar colors, and theme the menu from the chat colors. - Resolve outstanding PHPStan issues (gmdate guard, require_once ignore).
# Conflicts: # inc/Main.php # src/frontend/App.js Co-authored-by: HardeepAsrani <2649903+HardeepAsrani@users.noreply.github.com>
…g-responses Co-authored-by: HardeepAsrani <2649903+HardeepAsrani@users.noreply.github.com>
Add the hyve_chat_reply_data filter on both the streaming and poll reply paths so extensions can attach extra data to a reply, and generalize the frontend suggestion rendering into renderSuggestions so per-turn chips reuse the predefined-questions UI. Chips are built with textContent to avoid markup injection and scrolled into view after the reply lands. Part of Codeinwp/hyve#184.
Soare-Robert-Daniel
approved these changes
Jul 7, 2026
HardeepAsrani
changed the base branch from
feat/streaming-responses
to
development
July 8, 2026 20:26
Member
Author
|
@copilot resolve the merge conflicts in this pull request |
…-questions Co-authored-by: HardeepAsrani <2649903+HardeepAsrani@users.noreply.github.com>
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.
What this adds
The Hyve Lite base for per-turn suggestion chips, used by the Pro follow-up questions feature. The generation and UI live in the Pro companion (Codeinwp/hyve#259); this PR is the shared groundwork.
Part of Codeinwp/hyve#184 (closed by the Pro companion PR).
Changes
hyve_chat_reply_datafilter on both reply paths (the streamingdoneevent inStream.phpandget_chatfor the poll fallback), so an extension can attach extra data to a reply. A filter that returns a non-array is ignored on both paths so it cannot corrupt the response.renderSuggestions()in the widget.addSuggestions(predefined questions) and the new per-turn follow-ups now share one renderer: it clears any prior chip row, builds each chip withtextContent(notinnerHTML) so nothing can inject markup, wires a click to send the question, and scrolls the freshly added chips into view.get_chatnow reportssuccessusing the sameanswereddecision the streaming path uses, so both paths agree.Manual QA