Skip to content

Mutations not being separated into folder #41

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

Closed
bynho opened this issue Sep 28, 2022 · 2 comments · Fixed by #43
Closed

Mutations not being separated into folder #41

bynho opened this issue Sep 28, 2022 · 2 comments · Fixed by #43
Assignees
Labels
bug Something isn't working p1 Max priority

Comments

@bynho
Copy link

bynho commented Sep 28, 2022

Hello, I saw that this issue was closed a few days ago (#30) however when I run graphman, everything is still being placed under the queries folder.

I tried it with other APIs, such as this one: https://graphql-compose.herokuapp.com/northwind/

The end result is something similar to the below, as can be seen, it has mutations but it is stored under the queries array.

Screenshot 2022-09-28 at 15 47 14

As a separate question (not sure where to ask / apologies if it should be a separate issue). Is there a way to organize the apis into named collections? i.e. authentication, checkout etc?

@nohehf
Copy link
Member

nohehf commented Oct 10, 2022

Hey thanks for opening the issue, I'll take a look at it ASAP! Tho for your second question I'm not sure I understand what's the matter, could you be more specific, please? Thanks

@nohehf nohehf added bug Something isn't working p1 Max priority labels Oct 10, 2022
@nohehf nohehf self-assigned this Oct 10, 2022
@nohehf
Copy link
Member

nohehf commented Oct 10, 2022

Fixed in #43, I invite you to create a new issue for your second question, with more details if possible! Thanks for pointing this out @bynho

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working p1 Max priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants