microsoftgraph / microsoftgraph/msgraph-beta-sdk-dotnet
Beta and official SDK should share the same ODataError type
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 112
- Forks
- 37
- Avg merge
- 14h 57m
- Merged PRs (30d)
- 3
Description
In our current solution we mix the usage of the official and beta Graph API, cause we use a few features that are currently only available within the beta. Within v4 this mix was really cumbersome due to the shared namespace (to get this to run you need to use package aliases and extern alias). So switching to an individual namespace for the beta package really improves the usage of it.
While upgrading our solution to the v5 SDK I see that the ODataError type exists in both SDKs, which leads to some more complicated codes at a few places, cause we have to catch both exception types to ensure everything works as expected.
It would be great if the ODataError could be moved to the core library just like it had been done for the PageIterator to make the parallel usage of both libraries even more simple.
Contributor guide
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 by comparing the ODataError definitions in the beta and official SDKs, then review the core-library PageIterator change linked in the issue. Trace how both SDKs reference and expose the type. Done means both SDKs share one core-library ODataError type so callers do not need to catch duplicate exception types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100