Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blazor MS Graph article updates #27875

Merged
merged 5 commits into from
Dec 10, 2022
Merged

Blazor MS Graph article updates #27875

merged 5 commits into from
Dec 10, 2022

Conversation

guardrex
Copy link
Collaborator

@guardrex guardrex commented Dec 9, 2022

Addresses #24615

Thanks @hanslai and @damienbod. I'm going to sleep on these updates overnight and make some final touches on Saturday morning. Because of the number of updates here, you might want to wait until after tomorrow morning and inspect the live topic after these updates merge.

@guardrex guardrex self-assigned this Dec 9, 2022
@guardrex
Copy link
Collaborator Author

Ok ... LGTM 🦖 for a set of cool updates 😎. The base use cases here are the same as before, so I'm not too crazy worried about a technical blunder at this point. I do want to get some eyes on this 👀, but I'm going to do that on the live topic with the new content layout for this guidance. For one thing, I'm making the main approaches ... Graph SDK vs. named HttpClient/Graph API ... less confusing by using a doc pivot. I want to see how that renders and see what peeps think about it.

I'm going to take this whole subject up with DR and Artak offline for further discussion about keeping/dropping the topic or moving it to the Azure/MSI docs.

@guardrex guardrex merged commit 700b181 into main Dec 10, 2022
@guardrex guardrex deleted the guardrex/blazor-wasm-graph branch December 10, 2022 11:53
Donciavas pushed a commit to Donciavas/AspNetCore.Docs that referenced this pull request Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant