Skip to content

Conversation

Saifallak
Copy link

@Saifallak Saifallak commented Jun 22, 2024

Description

before v2.x release i need this simple edit, as it's a breaking change.
More work towards the custom data widgets.
because i'm creating my custom widgets.
so I need the message config be passed too.

Checklist

  • The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
  • 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

Add MessageConfiguration to customMessageBuilder wherever you use it.

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

@vatsaltanna-simformsolutions
Copy link
Collaborator

I believe this requirement can be handled at the app level.

@Saifallak
Copy link
Author

I believe this requirement can be handled at the app level.

How?, any examples?
Because according to package implementation its noy possible

@aditya-css
Copy link
Collaborator

Hey @Saifallak,
Thank you for contributing. Adding a customData can be beneficial for any custom metadata as mentioned in the issue #354. The other things added in custom message builder can be avoided. Can you please let me know to if you can update accordingly?

@aditya-css aditya-css added the waiting-for-response Waiting for someone to response label Jun 26, 2025
@aditya-css
Copy link
Collaborator

Thank you for contributing. But, due to inactivity I have to close this PR. Please feel free to create a new PR with the mentioned chnages if you'd still like to contribute.

@aditya-css aditya-css closed this Sep 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting-for-response Waiting for someone to response
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants