microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
SimpleIvrBot - Update to latest 'Microsoft.Graph.Communications' packages.
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Has anyone managed to update SimpleIvrBot to the latest packages, updating to anything past 1.2.0.7270 breaks more than just the models, any help would be appreciated?
There seems to be no guidance on how to do this as there are breaking changes in the way the graph calls are made Kiota. I've also swapped out 'Sample.Common' to 'Sample.Common.V1'
Bot.cs
await this.GraphApiClient.SendAsync(this.RequestBuilder.Communications.Calls[callId].SubscribeToTone(callId).Request(), RequestType.Create, tenantId, scenarioId).ConfigureAwait(false);
Error:
Severity Code Description Project File Line Suppression State
Error (active) CS1955 Non-invocable member 'CallItemRequestBuilder.SubscribeToTone' cannot be used like a method.
using (HttpClient tempClient = GraphClientFactory.Create(authenticationWrapper))
Error:
Severity Code Description Project File Line Suppression State
Error (active) CS1503 Argument 1: cannot convert from 'Sample.Common.Authentication.AuthenticationWrapper' to 'Microsoft.Graph.GraphClientOptions'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Bot.cs and the two reported compiler errors around SubscribeToTone and GraphClientFactory. Review the Microsoft.Graph.Communications changes after 1.2.0.7270 and the Sample.Common.V1 migration; done means SimpleIvrBot builds and its Graph calls use the updated APIs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100