Skip to content
This repository was archived by the owner on Mar 20, 2023. It is now read-only.

Missing support for custom default field resolver #331

Closed
mhagmajer opened this issue Jun 26, 2017 · 4 comments
Closed

Missing support for custom default field resolver #331

mhagmajer opened this issue Jun 26, 2017 · 4 comments

Comments

@mhagmajer
Copy link
Contributor

API for this package doesn't allow providing custom default field resolvers.

See more at: graphql/graphql-js#865
@mhagmajer
Copy link
Contributor Author

@leebyron @wincent what do you guys think about this?

@mhagmajer mhagmajer mentioned this issue Aug 22, 2017
Merged
@mbrowne
Copy link

mbrowne commented May 4, 2018

Now that the above PR is merged, I'm guessing this issue can be closed? I found this issue by Googling and it looked unresolved but I guess it's resolved.

@IvanGoncharov
Copy link
Member

@mbrowne Yes your right it resolved in #382
But not released yet so I will close this issue after release.

@IvanGoncharov
Copy link
Member

IvanGoncharov commented Jun 6, 2019 •
edited
Loading

Released 🎉

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mbrowne @mhagmajer @IvanGoncharov