You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature] Separate Graph SDK interaction into own package #75
I don't want the bloat of the entire Graph SDK if I only need to do authentication.
Describe the solution
The Graph SDK isn't really needed for authentication. There is a smaller Graph.Auth package we can use to get the core constructs to enable the sign in flow to work. The rest of the Graph SDK consumption should be relegated to a separate package, Microsoft.Toolkit.Graph.Data (or something similar), upon which the other packages can depend on as needed.
Microsoft.Toolkit.Graph.Data
This package will manage how we leverage the Graph SDK and interact with the Graph APIs.
In addition, the Graph SDK occasionally has bugs. A layer of indirection will allow us to workaround any issues while maintaining a consistent usage pattern across the solution.
changed the title [-][Feature] Separate Graph SDK interaction into Data package[/-][+][Feature] Separate Graph SDK interaction into own package[/+]on Mar 15, 2021
Now the main CommunityToolkit.Net.Authentication package no longer relies on the Graph SDK. All Graph SDK interaction is relegated to the CommunityToolkit.Net.Graph package
Activity
[-][Feature] Separate Graph SDK interaction into Data package[/-][+][Feature] Separate Graph SDK interaction into own package[/+]shweaver-MSFT commentedon Mar 25, 2021
This was changed in PR #76.
Now the main
CommunityToolkit.Net.Authenticationpackage no longer relies on the Graph SDK. All Graph SDK interaction is relegated to theCommunityToolkit.Net.Graphpackage