Feature/thread creation slug name #2507
Closed
Conversation
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
10 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pull Request Type
What is in this change?
Optional slug and name params for workspace thread creation to use with api.
Additional Information
Without slug param there is no way to identify thread by some 3rd party uuid4 with api. It's possible to store somewhere additional relation of "3rd party uuid4 - threadSlug", but with having ability of defining thread slug manually - this will be not required - thread slug will be equal to "3rd party uuid" so it will be easy to get required thread.
With thread name definition - it will be easy to use UI as "admin tool for viewing results of api based chats "
Developer Validations
yarn lintfrom the root of the repo & committed changes