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

Add mentionedMessageTemplate field #91

Conversation

dev-nicelee
Copy link

@dev-nicelee dev-nicelee commented Dec 27, 2023

Description

In the current Sendbird SDK, mentionedMessageTemplate is not included when sending and receiving a message.

Due to the issue above, profanity filtered message with mentioned users cannot be received. I tried with the normal message from the API, it does include the profanity filtered message but not with the mentioned users.

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Send a message with mentioned users and profanities which should be filtered.
  • Receive a message with mentioned users and profanities which should be filtered.

Flutter 3.13.6 • channel stable • https://github.com/flutter/flutter.git
Framework • revision ead455963c (3 months ago) • 2023-09-26 18:28:17 -0700
Engine • revision a794cf2681
Tools • Dart 3.1.3 • DevTools 2.25.0

Test Configuration:

  • Flutter Version: 3.13.6
  • OS: iOS 17
  • Dart Version: Dart 3.1.3
  • SDK: sendbird_chat_sdk 4.1.2

@sf-tyler-jeong
Copy link
Collaborator

Hi! @dev-nicelee
I think this is not a issue regarding flutter chat sdk.
Please raise your issue to https://community.sendbird.com.
Thanks!

@dev-nicelee
Copy link
Author

dev-nicelee commented Jan 18, 2024

@sf-tyler-jeong

Afaik, the mentionedMessageTemplate can be fetched simply by adding a field in flutter chat sdk like the implementation in this PR.

Although, I don't know why this is not an issue, I'm closing this PR and will raise my issue to the community again like you said.

Thank for the comment.🤞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants