Complete the 4.0 removals list and document the Chat UI conversion - #23
Merged
Merged
Conversation
🔍 Previewhttps://1635bdfe-opendialog-docs.opendialog.workers.dev Built from |
The August 2026 deprecation block did not match config/opendialog/deprecations.php on origin/4.x — the registry the platform reads to render the deprecation warning on a scenario card. That warning links at this page, so every id in the registry has to be explained here. Corrected against the code, not the ticket prose: - Azure Custom QA moves from "deprecated" to removed in 4.0 - Conversation Analysis added; it was missing entirely - OpenAI language processor added to the 5.0 deprecation list Verified by diffing packages/core/src/InterpreterEngine/Interpreters/ between origin/3.x and origin/4.x: seven interpreters are gone, and PaLM with them. One registry entry is deliberately left off the page: a single-customer action whose component id embeds that customer's name. This repo and the rendered page are both public. The id is not customer-visible — the warning renders the generic registry label — so the omission costs that customer nothing. Also explains "frozen", which was not on the page at all and is customer-visible — a frozen component refuses new configurations, including via scenario import or duplication — and records that POST /acknowledge goes with the legacy webchat. Adds a Chat UI conversion how-to sourced from ConvertWebchatScenarioService and ConvertWebchat.vue rather than the plan docs, whose earlier revisions describe a copy-based conversion that was later reversed to in-place: the scenario keeps its ID, app key, aliases and publish state, the comments section is dropped, unrecognised settings are retained but inert, and the one remaining customer step is swapping the embed script src. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N2MrBCh9967vv9DQd2vtx4
stu-greenshoots
force-pushed
the
docs/4-0-removals-and-chat-ui-conversion
branch
from
September 3, 2026 11:11
4c0f837 to
0181305
Compare
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
1 participant
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.
The August 2026 "Deprecations and removals" block did not match
config/opendialog/deprecations.phponorigin/4.x— the registry the platform reads to render the deprecation warning on a scenario card.That warning is hardcoded to link at this page (
resources/opendialog-design-system/components/Scenarios/Scenario.vue), so every component id in that registry has to be explained here, or a customer follows the warning to a page that does not mention what they were warned about.Removals corrected
Verified against the code, not the ticket prose — by diffing
packages/core/src/InterpreterEngine/Interpreters/betweenorigin/3.xandorigin/4.x:interpreter.core.qa)interpreter.core.conversation_analysis)language_processor.core.open_ai)Seven interpreters are gone on
4.x(LUIS, QnA, Rasa, Lex, Dialogflow, AzureCustomQA, ConversationAnalysis), andPaLMLanguageModel.phpwith them.One registry entry deliberately omitted
A single-customer renamed action is in the registry but is not documented on the page: its component id embeds that customer's name, and both this repo and the rendered page are public.
This costs that customer nothing — the deprecation warning renders the registry
label, which is generic, so the id is never customer-visible. Worth knowing for the future: any new registry entry whose id embeds a customer name needs the same treatment, or a relabelled id.Also added
POST /acknowledge(old webchatAsyncController@acknowledge) goes with the legacy webchat. The Chat UI has no equivalent; its one/acknowledge/chatApireference has never routed and already 404s, so nothing regresses — but it was public surface.ConvertWebchatScenarioServiceandConvertWebchat.vuerather than the plan docs, whose earlier revisions describe a copy-based conversion that was later reversed to in-place. Covers: converted in place (keeps ID, app key, aliases, publish state), the comments section dropped, unrecognised settings retained but inert, and the one remaining customer step — swapping the embed script src, with a link to Interface settings.Verification
astro buildpasses (205 pages). Both site-absolute links resolve to real built pages and the same-page anchor resolves in the built HTML.scripts/routes.mjswas not run — it reads the gitignoredsource/SUMMARY.md, absent now the conversion pipeline is retired. No routes are added or changed by this PR.Findings written up in
MIGRATION-NOTES.md.🤖 Generated with Claude Code
https://claude.ai/code/session_01N2MrBCh9967vv9DQd2vtx4