Skip to content

Commit 8091575

Browse files
Merge pull request #263897 from Mohtasim/mbellah/doc_cleanup
Clean up reaction on Azure Doc
2 parents db359c7 + 9b059f8 commit 8091575

File tree

2 files changed

+0
-110
lines changed

2 files changed

+0
-110
lines changed

articles/communication-services/how-tos/calling-sdk/includes/manage-video/manage-video-web.md

Lines changed: 0 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -491,58 +491,3 @@ Limitations:
491491
- Sending the same camera in both CallAgent, isn't supported. They must be two different cameras.
492492
- Sending two different cameras with one CallAgent is currently not supported.
493493
- On macOS Safari, background blur video effects (from @azure/communication-effects), can only be applied to one camera, and not both at the same time.
494-
495-
## Send or receive a reaction from other participants
496-
[!INCLUDE [Public Preview Disclaimer](../../../../includes/public-preview-include.md)]
497-
Sending and receiving of reactions is in public preview and available as part of versions 1.18.1-beta.1 or higher.
498-
499-
Within Azure Communication Services you can send and receive reactions when on a group call:
500-
- Like :+1:
501-
- Love :heart:
502-
- Applause :clap:
503-
- Laugh :smile:
504-
- Surprise :open_mouth:
505-
506-
To send a reaction you'll use the `sendReaction(reactionMessage)` API. To receive a reaction message will be built with Type `ReactionMessage` which uses `Reaction` enums as an attribute.
507-
508-
You'll need to subscribe for events which provide the subscriber event data as:
509-
```javascript
510-
export interface ReactionEventPayload {
511-
/**
512-
* identifier for a participant
513-
*/
514-
identifier: CommunicationUserIdentifier | MicrosoftTeamsUserIdentifier;
515-
/**
516-
* reaction type received
517-
*/
518-
reactionMessage: ReactionMessage;
519-
}
520-
```
521-
522-
You can determine which reaction is coming from which participant with `identifier` attribute and gets the reaction type from `ReactionMessage`.
523-
524-
### Sample on how to send a reaction in a meeting
525-
```javascript
526-
const reaction = call.feature(SDK.Features.Reaction);
527-
const reactionMessage: SDK.ReactionMessage = {
528-
reactionType: 'like'
529-
};
530-
await reaction.sendReaction(reactionMessage);
531-
```
532-
533-
### Sample on how to receive a reaction in a meeting
534-
```javascript
535-
const reaction = call.feature(SDK.Features.Reaction);
536-
reaction.on('reaction', event => {
537-
// user identifier
538-
console.log("User Mri - " + event.identifier);
539-
// received reaction
540-
console.log("User Mri - " + event.reactionMessage.name);
541-
// reaction message
542-
console.log("reaction message - " + JSON.stringify(event.reactionMessage));
543-
}
544-
```
545-
546-
### Key things to note about using Reactions:
547-
- Reactions won't work if the meeting organizer updates the meeting policy to disallow the reaction in a Teams interop call.
548-
- Sending of reactions doesn't work on 1:1 calls.

articles/communication-services/how-tos/cte-calling-sdk/includes/manage-calls/manage-calls-web.md

Lines changed: 0 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -345,58 +345,3 @@ Recommendations for the management of chat ID:
345345
- Escalation of the 1:1 phone call by adding another phone participant: Use Graph API to get the existing chat ID with only Teams user as a participant or create a new group chat with participants: Teams user ID and "00000000-0000-0000-0000-000000000000"
346346
- Group call with single Teams user and multiple phone participants: Use Graph API to get existing chat ID with only Teams user as a participant or create a new group chat with participants: Teams user ID and "00000000-0000-0000-0000-000000000000"
347347
- Group call with more than 2 Teams users: Use Graph API to get or create a group chat with the Teams users
348-
349-
## Send or receive a reaction from other participants
350-
> [!NOTE]
351-
> This API is provided as a preview for developers and may change based on feedback that we receive. To use this api please use 'beta' release of Azure Communication Services Calling Web SDK version 1.18.1 or higher
352-
353-
Within Azure Communication Services you can send and receive reactions when on a group call:
354-
- Like :+1:
355-
- Love :heart:
356-
- Applause :clap:
357-
- Laugh :smile:
358-
- Surprise :open_mouth:
359-
360-
To send a reaction you'll use the `sendReaction(reactionMessage)` API. To receive a reaction message will be built with Type `ReactionMessage` which uses `Reaction` enums as an attribute.
361-
362-
You'll need to subscribe for events which provide the subscriber event data as:
363-
```javascript
364-
export interface ReactionEventPayload {
365-
/**
366-
* identifier for a participant
367-
*/
368-
identifier: CommunicationUserIdentifier | MicrosoftTeamsUserIdentifier;
369-
/**
370-
* reaction type received
371-
*/
372-
reactionMessage: ReactionMessage;
373-
}
374-
```
375-
376-
You can determine which reaction is coming from which participant with `identifier` attribute and gets the reaction type from `ReactionMessage`.
377-
378-
### Sample on how to send a reaction in a meeting
379-
```javascript
380-
const reaction = call.feature(SDK.Features.Reaction);
381-
const reactionMessage: SDK.ReactionMessage = {
382-
reactionType: 'like'
383-
};
384-
await reaction.sendReaction(reactionMessage);
385-
```
386-
387-
### Sample on how to receive a reaction in a meeting
388-
```javascript
389-
const reaction = call.feature(SDK.Features.Reaction);
390-
reaction.on('reaction', event => {
391-
// user identifier
392-
console.log("User Mri - " + event.identifier);
393-
// received reaction
394-
console.log("User Mri - " + event.reactionMessage.name);
395-
// reaction message
396-
console.log("reaction message - " + JSON.stringify(event.reactionMessage));
397-
}
398-
```
399-
400-
### Key things to note about using Reactions:
401-
- Reactions won't work if the meeting organizer updates the meeting policy to disallow the reaction in a Teams interop call.
402-
- Sending of reactions doesn't work on 1:1 calls.

0 commit comments

Comments
 (0)