Add full template model support #262
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We introduce typed template message with full components support (header, body and buttons) and adapt the interactive message (from webhook) to also accomodate template button responses modeled as interactive message selections too (for simplicity). This also implied renaming Selection.Id => Value and Title > Text since those are more generic and accomodate all three user-interactive responses (so far). Further breaking changes may happen down the road as we implement Flows too.
Member
Author
|
🧪 Details on Ubuntu 24.04.2 LTSfrom dotnet-retest v0.7.2 on .NET 9.0.7 with 💜 by @devlooped |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We introduce typed template message with full components support (header, body and buttons) and adapt the interactive message (from webhook) to also accomodate template button responses modeled as interactive message selections too (for simplicity).
This also implied renaming Selection.Id => Value and Title > Text since those are more generic and accomodate all three user-interactive responses (so far).
Further breaking changes may happen down the road as we implement Flows too.