Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Other]: Can the new message callback provide the conversationID of which conversation it belongs to #1882

Closed
LJFDBXJ opened this issue Feb 4, 2024 · 2 comments
Closed

[Other]: Can the new message callback provide the conversationID of which conversation it belongs to #1882

LJFDBXJ opened this issue Feb 4, 2024 · 2 comments
Labels
other Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@LJFDBXJ
Copy link

LJFDBXJ commented Feb 4, 2024 •
edited by skiffer-git
Loading

What would you like to share?

Can the new message callback provide the conversationID of which conversation it belongs to? It will be needed for querying the conversation list later.

Additional information

No response
@LJFDBXJ LJFDBXJ added the other Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 4, 2024
@skiffer-git skiffer-git changed the title [Other]: <消息回调> [Other]: Can the new message callback provide the conversationID of which conversation it belongs to Feb 5, 2024
@kubbot
Copy link
Contributor

kubbot commented Apr 6, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot
Copy link
Contributor

kubbot commented Apr 14, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
other Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LJFDBXJ @kubbot