Add reaction message support, improve type safety #35
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 were not surfacing reaction messages separately. This now allows processing user reactions separately from other message types. Also, type safety when doing Reply and MarkRead wasn't great since users could attempt either operation on a message that doesn't support that kind of interaction (such as status or error messages). So we create two intermediate types, UserMessage (the ones users can interact with, like content and interactive messages), and SystemMessage (reaction, status, error and unsupported). We also fix the sample to properly report the environment which for some reason is not Development despite envvars being set properly by the Azure Functions tools on local run.
Member
Author
|
🧪 Details on Ubuntu 24.04.2 LTSfrom dotnet-retest v0.7.1 on .NET 8.0.15 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 were not surfacing reaction messages separately. This now allows processing user reactions separately from other message types.
Also, type safety when doing Reply and MarkRead wasn't great since users could attempt either operation on a message that doesn't support that kind of interaction (such as status or error messages). So we create two intermediate types, UserMessage (the ones users can interact with, like content and interactive messages), and SystemMessage (reaction, status, error and unsupported).
We also fix the sample to properly report the environment which for some reason is not Development despite envvars being set properly by the Azure Functions tools on local run.