Skip to content

Releases: Azure-Samples/communication-services-web-chat-hero

UI Library based hero sample using @azure/communication-react@1.18.1

11 Sep 17:33
358bfa7
Compare
Choose a tag to compare

Update the UI library dependency to v1.18.1

UI Library based hero sample using @azure/communication-react@1.18.0

23 Jul 16:04
57027ba
Compare
Choose a tag to compare

UI Library based hero sample using @azure/communication-react@1.17.0

10 Jun 22:52
1042d06
Compare
Choose a tag to compare
Merge pull request #152 from Azure-Samples/palatter/1.17.0-update

Update to communication-react 1.17.0

UI Library based hero sample using @azure/communication-react@1.16.1

31 May 22:34
790453d
Compare
Choose a tag to compare

UI Library based hero sample using @azure/communication-react@1.14.0

22 Mar 17:22
1c1b52e
Compare
Choose a tag to compare

UI Library based hero sample using @azure/communication-react@1.12.0

18 Jan 22:43
c3df7b9
Compare
Choose a tag to compare

UI Library based hero sample using @azure/communication-react@1.8.0

11 Nov 03:04
fb40d1e
Compare
Choose a tag to compare

UI Library based hero sample using @azure/communication-react@1.7.0

22 Aug 00:02
003e09a
Compare
Choose a tag to compare

This release updates the sample to use new core UI library dependency: @azure/communication-react@1.7.0 as well as other dependency updates.
Full Changelog: 79bbeb7...1.7.0

Updating server code to take in an adminUserId

29 Dec 17:55
79bbeb7
Compare
Choose a tag to compare

There was an issue where if you were using chat threads in this sample and you restarted the server then you wouldn't be able to access the old chat threads.

This is because Azure Communications Service requires a user to add other users to a chat thread before they can participate. In a previous iteration we had dynamically created a user per thread. Now we are explicitly having developers enter their own "user id" from their Azure Communications Service resource. This user will be used to create all new threads and invite any new users to that chat thread. This will also mean that since the user is "static" then if the server restarts then we will still have access to previously created threads because we still have a reference to that user.

You can create an identity quickly in Azure Portal. Check out this link to learn more.
https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/identity/quick-create-identity

UI Library based hero sample using @azure/communication-react@1.4.1

01 Dec 00:42
6147468
Compare
Choose a tag to compare

This release updates the sample to use new core UI library dependency: @azure/communication-react@1.4.1 as well as other dependency updates.

Full Changelog: 1.4.0...1.4.1