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

(Maybe) GraphQL playground as dynamic docs #23

Open
EvgeniiaVak opened this issue Nov 20, 2020 · 5 comments
Open

(Maybe) GraphQL playground as dynamic docs #23

EvgeniiaVak opened this issue Nov 20, 2020 · 5 comments

Comments

@EvgeniiaVak
Copy link
Contributor

When studying GraphQL with node-js I was able to explore the underlying graphql schema with the interactive documentation via GraphQL playground (based on GraphQL schema, all items are clickable there):

image

Hasura also has something like this via their console app, maybe it'd be possible to expose that as the API documentation:
https://hasura.io/learn/graphql/hasura/data-modelling/4-try-todos-queries/
graphql-query-todo

So maybe to autogenerate API docs we could wire up one of those?

@EvgeniiaVak
Copy link
Contributor Author

cc @leomrocha @rufuspollock @anuveyatsu ^

@rufuspollock
Copy link
Member

@EvgeniiaVak i think this is a great idea - are you suggesting we enable this by default on the base API page or somewhere else?

@EvgeniiaVak
Copy link
Contributor Author

I don't really know, somewhere, the nodejs wrapper has datastore_search endpoint also which is not graphql, so it wouldn't be right to put only graphql docs in the base API page, maybe on the base API page we could have links to two docs - one for the REST endpoint, the other - to graphql

@leomrocha
Copy link
Contributor

I really like this, I would make it as a separate service or plugin that can be deployed with the data-api.

I don't really know, somewhere, the nodejs wrapper has datastore_search endpoint also which is not graphql, so it wouldn't be right to put only graphql docs in the base API page, maybe on the base API page we could have links to two docs - one for the REST endpoint, the other - to graphql

Concerning the documentation, I also think that separating it in maybe two files REST.md and GRAPHQL.md would be a nice thing.

@rufuspollock
Copy link
Member

@leomrocha / @EvgeniiaVak can you add tasks and acceptance items to the task to summarize what work would be needed.

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

3 participants