Skip to content

Conversation

@JoeHartzell
Copy link
Contributor

This should fix #47.

I added the context as a parameter to the NodeGraphType.GetById method. I also had to fix all the example projects as this is a breaking change.

@sungam3r sungam3r added enhancement New feature or request BREAKING Breaking changes in either public API or runtime behavior labels Apr 17, 2021
@sungam3r sungam3r added this to the v1.0 milestone Apr 17, 2021
This was referenced Apr 26, 2021
@Shane32 Shane32 modified the milestones: v1.0, v0.6.0 Apr 28, 2021
@JoeHartzell
Copy link
Contributor Author

@Shane32 Got some time to get back to this. I made the context come first as we were discussing in the conversation above. I think it makes more sense as the context seems to come first in many other places.

@Shane32
Copy link
Member

Shane32 commented Apr 30, 2021

@JoeHartzell thanks! if you can merge in the latest changes from master it would be helpful. Thanks!!

@Shane32 Shane32 merged commit 35e434f into graphql-dotnet:master May 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BREAKING Breaking changes in either public API or runtime behavior enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GetById() requiring context

3 participants