Refactor targeted messaging API to consolidate recipient and targeting flags #449
+117
−59
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.
Applies the targeted messaging API refactor from microsoft/teams.net#318. The change consolidates
withTargetedRecipient()into an enhancedwithRecipient()method, making targeted message creation more explicit and reducing API surface area.API Changes
Before:
After:
Implementation
isTargetedfromMessageActivityto baseActivityclass as non-nullable boolean (defaultfalse)Activity.withRecipient(account, isTargeted?)to accept optional targeting flagMessageActivity.withTargetedRecipient()methodBreaking Changes
The
withTargetedRecipient()method is removed. Callers must migrate towithRecipient(account, true).✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.