Ideas for graphql-cli v3 about graphql-cli HOT 4 CLOSED

Adding more commands to manage configuration

For example, commands to manage endpoints (from #9)

• graphql endpoint add (with the current add-endpoint as alias for backwards compatibility)
• graphql endpoint set header
• graphql endpoint remove header
• graphql endpoint set url

Also, add the option to ask for or specify headers on add-endpoint/endpoint add.

from graphql-cli.

I see that some of the ideas might apply, however it will be better to have them logged as separate issues. Closing but feel free to reopen or create separate issue with idea that our team can implement

from graphql-cli.

Passing context to commands

The current implementation using a custom handler wrapper to pass in context to the commands. This makes it harder to work with the standard CommandObject interface, and it also makes it harder to test individual commands in isolation.

Yargs offers a standard way of passing context to commands, using the parse function that I think should be used instead of the custom handler wrapper.

from graphql-cli.

If we add a watch mode, I think it would be good to clear the console before downloading any changes. This helps clear the air on if there are any errors from one download to the next.

from graphql-cli.