graphql-tools

An improve to the layout of the devtool could definitely improve user experience. Lets make sure the devtool is utilizing the space better.

Add a GitHub action flow for publishing a new version (run build, run tests, publish to npm and GitHub packates) etc.

https://github.com/sisense/graphql2rest/actions/new

It seems like graphql parser doesn't like graphql comments in the schemas? This is using the federated proxy example.

build base schema: parse graphql document string: external: unexpected token - got: COMMENT want one of: [], locations:

remote schema

input UserInput {
    userID: Int
	# Some comment
	place: String
}

The fluent API seems to try to mimic natural language, e.g.

 isThis(error)
 .UserNotFoundError(() => ...)
 .NotAProphetError(() => ...)

errorHere(*error*) uses the following construct:

 if(errorHere(error).isNotAProphetError){
   // Do something
 } else if(errorHere(error).isProphetNotFoundWithId){
   // Do something else
 }

would

`thisError(error).i