Feat: support conversationId field in ChatGPTAPI.sendMessage option #505
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.
Expect to specify
conversationId
in option ofsendMessage
, ChatGPTAPI .So we can support multi-conversation chat。After message save, query whole conversation infomation according to fieldname:
conversationId
from custom database, rather than last message'sparentMessageId
.In fact, there are serveral conversation in the same database(maybe mysql, mongodb), every message in one conversation should has same identity, so that they can quickly be found / deleted。
Usage like:
Then query them: