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.

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: fix replied message showing no content across different connection modes #194

Merged
merged 1 commit into from
Nov 2, 2024

Conversation

dev-737
Copy link
Member

@dev-737 dev-737 commented Nov 2, 2024

Simplify the storeMessageData function by removing the unused mode
parameter and refactoring the await storeMessageData call in
MessageCreate to use fewer arguments. Address error handling in the
storeMsgTimestamps task by adding a FIXME comment for a specific
error case. Additionally, enhance the error response logic in the
EditMessage command to improve user feedback during modal
interactions.

…on modes

Simplify the `storeMessageData` function by removing the unused `mode` 
parameter and refactoring the `await storeMessageData` call in 
`MessageCreate` to use fewer arguments. Address error handling in the 
`storeMsgTimestamps` task by adding a FIXME comment for a specific 
error case. Additionally, enhance the error response logic in the 
`EditMessage` command to improve user feedback during modal 
interactions.
@dev-737 dev-737 merged commit 3cbdf56 into main Nov 2, 2024
5 checks passed
@dev-737 dev-737 deleted the Lane-2 branch November 2, 2024 05:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant