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

Expose the fields of GraphQLRequest #750

Closed
sessionboy opened this issue Aug 31, 2020 · 3 comments
Closed

Expose the fields of GraphQLRequest #750

sessionboy opened this issue Aug 31, 2020 · 3 comments
Assignees
Labels
enhancement Improvement of existing features or bugfix

Comments

@sessionboy
Copy link

sessionboy commented Aug 31, 2020

Describe the solution you'd like

My database is dgraph, which is a native graphql database.
I need to query the data of dgraph graphql database in the juniper server. This is not as easy as restful.

So i want to get query, operation_name and variables because I want to request data from dgraph graphql database based on them. But now they are private.

In addition, how can I obtain resolveInfo? Maybe I need it.

@sessionboy sessionboy added the enhancement Improvement of existing features or bugfix label Aug 31, 2020
@LegNeato
Copy link
Member

Hmm, I thought operation name was public, perhaps it got dropped:

https://github.com/graphql-rust/juniper/pull/265/commits

@sessionboy
Copy link
Author

@LegNeato I checked the source code, they are private and I cannot get them. Can you update and publish it ?

@mkpankov
Copy link

mkpankov commented Sep 3, 2020

I think I need this too. Say user wants a subfield { details { foo, bar } }. I need a different query for PostgreSQL to fetch details. Right now I have a query argument detail: bool, but I really should determine if user asked for details and change logic automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement of existing features or bugfix
Projects
None yet
Development

No branches or pull requests

4 participants