RFC: Chat Extension v2 — Extendable Chat System#13
Open
filvecchiato wants to merge 1 commit into
Open
Conversation
4 tasks
filvecchiato
changed the title
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.
RFC: Chat Extension v2 — Extendable Chat System
Summary
Replaces Chat Extension v1 with a new architecture where Products control the chat experience (data source, handlers, actions) while the Host provides the UI shell and sensible defaults.
Checklist
docs/rfcs/0002-chat-extension-v2.mdwith completed frontmatterdocs/rfcs/_index.mdwith a link to the new RFCrfc,proposalMotivation
Chat Extension v1 had a host-owned message store, fixed chat structure, no scalability path, and a rigid participant model. v2 inverts control so Products decide how messages are stored, fetched, and acted upon. Migrated from paritytech/triangle-js-sdks#79.