You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2021. It is now read-only.
As a developer, I want to move the chat protocol implementation to a separate Go repo so that we realize performance improvements and better architectural separation (e.g. we'd be able to replace the SDK implementation with a mock implementation to test having large sets of data in the react app UI).
Implementation
TODO: Known steps towards feature implementation.
What needs further specifying and investigating.
Acceptance Criteria
Simplified API is available in the Go SDK allowing the react repo to easily consume the chat functionality. There should be no breaking changes or UX changes required.
Notes
TODO: Random notes to keep in mind while implementing it. Mostly about related issues and future plans and thoughts.
Problem
As a developer, I want to move the chat protocol implementation to a separate Go repo so that we realize performance improvements and better architectural separation (e.g. we'd be able to replace the SDK implementation with a mock implementation to test having large sets of data in the react app UI).
Implementation
TODO: Known steps towards feature implementation.
What needs further specifying and investigating.
Acceptance Criteria
Simplified API is available in the Go SDK allowing the react repo to easily consume the chat functionality. There should be no breaking changes or UX changes required.
Notes
TODO: Random notes to keep in mind while implementing it. Mostly about related issues and future plans and thoughts.
Future Steps
The text was updated successfully, but these errors were encountered: