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

Feature: show input types #37

Open
ecerroni opened this issue Sep 19, 2017 · 6 comments
Open

Feature: show input types #37

ecerroni opened this issue Sep 19, 2017 · 6 comments

Comments

@ecerroni
Copy link

This tool is awesome! Are you planning to parse input types as well?

@IvanGoncharov
Copy link
Member

@ecerroni Thank you for feedback 👍
What kind of visualization you have in mind?
Do you want input types to be represented on the graph or only on documentation panel?

@ecerroni
Copy link
Author

Mhm, good question. I guess having them on both the graph and the documentation panel would be great.

However it depends on you as a maintainer. This is obviously not critical and I consider it as at the same level of the feature request about having a switching button for Query vs Mutation.

Voyager is already terrific! Thus you know best what to prioritize on the roadmap :)

@Harmonickey
Copy link

This would be super valuable, as icing on the cake here.

@danpalmer
Copy link

@IvanGoncharov I see that in a recent version selection of the graph root has been added, but "Mutation" is not showing up there for me. Is this expected?

@IvanGoncharov
Copy link
Member

@danpalmer If your API has "Mutation" than it should be shown right after "Query" at the top of the list.
You can check if your API has a mutation root by executing:

{
  __schema {
    mutationType {
      name
    }
  }
}

@danhorvath
Copy link

First of all great work, this is a super nice tool!
It seems there's not too much activity on this issue - is there any update on this feature request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants