Request: abstracted chat surface, not just Slack - #556
Open
Luke20w wants to merge 1 commit into
Open
Conversation
Chat isn't behind a generic interface the way harnesses, session stores, and sandboxes are, so a company on Teams (or anything but Slack) can't plug in without rebuilding the whole surface.
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.
Request: Abstracted chat surface, not just Slack
My company uses Teams (unforgiveable, I know :) ) so a ton of the benifet of QM is locked away. I'm sure there's others out there in a similar situation.
From what I can tell, chat isn't behind a generic interface the way harnesses, session stores, and sandboxes are. I'd like the chat surface itself to become a real substrate abstraction so Teams (and whatever comes after) can plug
in easily
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.