Skip to content

feat: ✨Customising pre-defined texts. #307

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

rishabhsimformsolutions
Copy link
Contributor

@rishabhsimformsolutions rishabhsimformsolutions commented Jan 16, 2025

Description

Added two string fields respectively to update the sending and replying text, if not provided will take default Strings from the string.dart file.

Checklist

  • The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
  • I have followed the Contributor Guide when preparing my PR.
  • I have updated/added tests for ALL new/updated/fixed functionality.
  • I have updated/added relevant documentation in docs and added dartdoc comments with ///.
  • I have updated/added relevant examples in examples or docs.

Breaking Change?

The changes in the PR introduces two parameters in sending and replying message configurations to allow users to customise pre-defined texts when replying and sending messages. If not defined, the application would use the pre-defined texts.

  • Yes, this PR is a breaking change.
  • No, this PR is not a breaking change.

Related Issues

#296

@@ -65,6 +65,12 @@ class RepliedMessageConfiguration {
/// Used to give opacity of replied message.
final double? opacity;

/// Used to give user define custom text to "Replied By" text.
final String? customRepliedByText;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as we can have multiple text please create a model

@vatsaltanna-simformsolutions
Copy link
Collaborator

improve commit message

@vatsaltanna-simformsolutions
Copy link
Collaborator

need to solve the issue through translation instead of parameter

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.

2 participants