Retrieve conversation list from ConversationStore and agent trait#236
Open
barryvdh wants to merge 3 commits intolaravel:0.xfrom
Open
Retrieve conversation list from ConversationStore and agent trait#236barryvdh wants to merge 3 commits intolaravel:0.xfrom
barryvdh wants to merge 3 commits intolaravel:0.xfrom
Conversation
Author
|
Not sure if we want to return it as array like messages, or collection (from the trait). And maybe we should include the created_at / updated_at? |
Member
|
I wonder if this should be traits you can add on to your |
Author
|
I guess that would make sense and make it easier to handle the conversations/messages |
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.
This allows to get the list of the conversation from the ConversationStore and use this in the
RemembersConversationstrait.This makes it possible to get the list of conversation to resume in the UI, without calling the database directly.
Note: this is a BC break for any other store implementations, so would require a SemVer bump (if anyone implements their own store).