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

What is point of calling serviceCollection.AddDapperGraphQL? #39

Open
davihar opened this issue Apr 18, 2019 · 1 comment
Open

What is point of calling serviceCollection.AddDapperGraphQL? #39

davihar opened this issue Apr 18, 2019 · 1 comment

Comments

@davihar
Copy link

davihar commented Apr 18, 2019

Hi, what is the point of calling serviceCollection.AddDapperGraphQL? Looking at the test project, it does not look like any of the added instances are ever retrieved via serviceProvider.GetRequiredService calls. I've also seen an example work without using AddDapperGraphQL.

Please explain and/or add an example to the readme file explaining why one would use AddDapperGraphGL.

Thanks

@infogulch
Copy link

It appears that AddDapperGraphQL is there to help you add your own DI types so that they can be DI'd correctly. It does this via the DapperGraphQLOptions class.

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

No branches or pull requests

2 participants