Skip to content

Commit e778110

Browse files
address PR comments
1 parent 9ebf9b9 commit e778110

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/communication-services/concepts/raw-id-use-cases.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ CommunicationIdentifier has the following advantages:
2424
- Allows using a switch case by type to address different application flows.
2525
- Allows restricting communication to specific types.
2626

27-
On top of this, the *CommunicationIdentifier* and the derived types (`MicrosoftTeamsUserIdentifier`, `PhoneNumberIdentifier`, etc.) can be converted to its string representation (Raw ID), making the following scenarios easier to implement:
27+
On top of this, the *CommunicationIdentifier* and the derived types (`MicrosoftTeamsUserIdentifier`, `PhoneNumberIdentifier`, etc.) can be converted to its string representation (Raw ID) and restored from the string, making the following scenarios easier to implement:
2828
- Extract identifier details from Raw IDs and use them to call other APIs (such as the Microsoft Graph API) to provide a rich experience for communication participants.
2929
- Store identifiers in a database and use them as keys.
3030
- Use identifiers as keys in dictionaries.
@@ -228,7 +228,8 @@ function CommunicationParticipants() {
228228
return (
229229
<div>
230230
{users.map((user) => (
231-
// Each list item should have a unique key. Raw ID can be used as such key.
231+
// React uses keys as hints while rendering elements. Each list item should have a key that's unique among its siblings.
232+
// Raw ID can be utilized as a such key.
232233
<ListUser item={user} key={user.id} />
233234
))}
234235
<button onClick={() => setUsers(users.slice().reverse())}>Reverse</button>

0 commit comments

Comments
 (0)