Urigo/graphql-cli

graphql accepts arbitrary commands without throwing

hediet opened this issue · 1 comments

hediet commented

Describe the bug
yarn graphql foobar runs through and does not indicate an error, even though foobar does not exist.

To Reproduce
Steps to reproduce the behavior:

  1. Install graphql 4.1.0
  2. Run yarn graphql foobar

Expected behavior
The tool should output an error that the command foobar does not exist.

Screenshots

image

Versions (please complete the following information):

  • OS: Windows 10
  • graphql-cli: 4.1.0
melMass commented

@Urigo Is there a practical reasoning behind that design decision?