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

Allow own ITypeTesolver #134

Merged
merged 5 commits into from
Mar 5, 2019
Merged

Allow own ITypeTesolver #134

merged 5 commits into from
Mar 5, 2019

Conversation

BilyachenkoOY
Copy link
Contributor

See issue #132 and commit messages for details

Change `GraphQLEngine` and `RequestHandler` to use type resolver interface instead of class to allow to change their behaviour and provide own implementation.
Add possibility to override methods of `TypeResolver` instead of creating completelly new implementation;
make `ObjectReflector` protected inside `partial class TypeResolver` so that it will be accessable to derived classes.
Copy link
Collaborator

@tlil tlil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks!

@tlil tlil merged commit 27a5ab2 into graphql-dotnet:master Mar 5, 2019
@tlil
Copy link
Collaborator

tlil commented Mar 5, 2019

Thanks, @BilyachenkoOY - I'll bump the version number a bit later today so that you can consume the updates through NuGet.

@tlil
Copy link
Collaborator

tlil commented Mar 8, 2019

This is now published as 2.0.3 , @BilyachenkoOY

@BilyachenkoOY BilyachenkoOY deleted the allow-own-ITypeResolver branch March 13, 2019 07:47
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.

2 participants