-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Fix: Incorrect event topic for chat message deletion #3202
Comments
Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues. |
Can I work on this issue? |
this hasn't been approved yet ig not a valid issue by rabbitai . wait for checks |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue. |
i would like to work on this issue |
This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue. |
Unassigning due to inactivity and/or no submitted PR. Others need to get a chance. Please let us know whether you want to be reassigned before someone else requests assignment or select another issue. |
The event topic in deleteChatMessage resolver uses ':chat_messages::create' for deletion operations, which is incorrect and could cause confusion for subscribers.
Current Behavior
The current implementation publishes deletion events with topic 'chats.[chatId]:chat_messages::create'
Expected Behavior
Deletion events should use topic 'chats.[chatId]:chat_messages::delete' to accurately reflect the operation type.
Context
This should be addressed in a separate PR focused on server-side improvements.
The text was updated successfully, but these errors were encountered: