microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Id not set on Call resource object by Notification processor with latest beta packages
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Describe the issue
We upgraded to latest Graph SDK packages and the biggest change for us is that they moved from NewtonSoft.Json to System.Text.Json. This is all fine with us, however the Call.Id property is not populated anymore from the notification requests, causing our application to be unable to handle the updates properly.
Expected behavior
Call.Id populated by the NotificationProcessor for all notifications.
Graph SDK:
- Microsoft.Graph.Communications.Core 1.2.0.4209 (beta)
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 the NotificationProcessor handling of notification requests and compare deserialization behavior between Newtonsoft.Json and System.Text.Json in Microsoft.Graph.Communications.Core 1.2.0.4209-beta. Verify how the Call resource is populated, especially Call.Id. Done means Call.Id is populated for all notifications and the application can handle updates correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100