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

feat!: putting the replied message widget builder inside the reply message widget #135

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

Conversation

reliance-engineer
Copy link

@reliance-engineer reliance-engineer commented Dec 22, 2023

Description

I put the repliedMessageWidgetBuilder inside the ReplyMessageWidget.

This allows to keep the scroll action when tapping the reply message.

Also I modified the RepliedMessageConfiguration to add a callback for those who what to modify the behaviour of the tap gesture

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?

Migration instructions

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

If any developer was implementing RepliedMessageConfiguration.repliedMessageWidgetBuilder they should know it's now behing the ReplyMessageWidget and not outside, soy they should provide the RepliedMessageConfiguration.onReplyTapped parameter to control the tap action on the replied message.

If you want to scroll to the replied message then you don't need to do anything.

…sage widget

This allows to keep the scroll action when tapping the reply message.

Also I modified the RepliedMessageConfiguration to add a callback for those who what to modify the behaviour of the tap gesture
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