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

[Feature] Add GraphPresenter to help with general calls to the Graph #17

Closed
michael-hawker opened this issue Oct 20, 2019 · 1 comment · Fixed by #18
Closed

[Feature] Add GraphPresenter to help with general calls to the Graph #17

michael-hawker opened this issue Oct 20, 2019 · 1 comment · Fixed by #18
Milestone

Comments

@michael-hawker
Copy link
Member

Describe the problem this feature would solve

Analogous to MGT Issue #160 here

Have a generalized component to aid in making graph calls within XAML for controls that we don't have yet.

Describe the solution

Create a GraphPresenter control which inherits from ContentPresenter. By providing it a call to the graph, it will go fetch data from the graph and set its contents to the result.

This will allow the developer to setup a DataTemplate in order to display the proper data.

Additional context & Screenshots

Screenshot of initial prototype:
image

Advantage of this proposed approach is that everything is still strongly typed to the Graph .NET SDK. 🦙

@michael-hawker
Copy link
Member Author

Probably should investigate using IncrementalLoadingCollection from the Toolkit for the paging aspect of this?

@ghost ghost added the In-PR 🚀 label Jul 27, 2020
azchohfi added a commit that referenced this issue Aug 11, 2020
…enter

Initial GraphPresenter prototype for #17
@ghost ghost added Completed 🔥 and removed In-PR 🚀 labels Aug 11, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Sep 10, 2020
@shweaver-MSFT shweaver-MSFT added this to the 7.1.0 milestone Aug 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants