Adds reaction management capabilities via the Bot Framework API v3, mirroring the teams.net implementation.

Changes

ReactionClient (/packages/api/src/clients/reaction/)

• add(conversationId, activityId, reactionType) - PUT to /v3/conversations/{conversationId}/activities/{activityId}/reactions/{reactionType}
• remove(conversationId, activityId, reactionType) - DELETE to same endpoint
• Integrated into main Client class as reactions property

ReactionType Model (/packages/api/src/models/reaction/)

• Type-safe reaction values: 'like' | 'heart' | 'laugh' | 'surprised' | 'sad' | 'angry'

Breaking Change: MessageReactionActivity

• Removed addReaction() and removeReaction() helper methods
• Reactions should now be managed via ReactionClient or set directly on activity properties

Example Application (/examples/reactions/)

• Added comprehensive example bot demonstrating ReactionClient usage
• Shows how to add/remove reactions programmatically
• Demonstrates handling messageReaction activity events
• Includes interactive commands and detailed documentation

Usage

import { Client } from '@microsoft/teams.api';

const client = new Client(serviceUrl);

// Add a reaction
await client.reactions.add('conversationId', 'activityId', 'like');

// Remove a reaction
await client.reactions.remove('conversationId', 'activityId', 'like');

// MessageReactionActivity now requires direct property assignment
const activity = new MessageReactionActivity({
  reactionsAdded: [{ type: 'like', user: account }],
  reactionsRemoved: [{ type: 'heart', user: account }],
});

See the examples/reactions directory for a complete working example.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.