VaporMiddleware responding incorrectly to all paths about pioneer HOT 7 CLOSED

Looks like a bug on my part, I'll have a look and see why the GraphQL Middleware is responding on a different path

from pioneer.

Is this happening for both GET and POST request?

from pioneer.

Yes

from pioneer.

I have an existing simple GraphQL server running and I added some few non-GraphQL routes, I couldn't get Pioneer to respond to any of those non-GraphQL endpoints and reproduce. Can you share a bit more on this bug such as:

• Some example of the REST endpoints
• The HTTP method of the request or a sample HTTP request being made
• Where did you add the VaporMiddleware and is it before or after the REST endpoints where set up
• What did you pass in in the VaporMiddleware options

from pioneer.

Yes

Right, so it's just the middleware somehow ignoring the path

from pioneer.

I found what is the problem. I wrote a separate middleware to get a list of fields and further select these fields through Fluent, it accesses graphql in Request and gives an error. For some reason this problem didn't exist before version 1

from pioneer.

I found what is the problem. I wrote a separate middleware to get a list of fields and further select these fields through Fluent, it accesses graphql in Request and gives an error. For some reason this problem didn't exist before version 1

I'm glad you managed to resolve the issue.

Version 1 is in fact a bit more strict and verbose on errors from decoding GraphQL Request as to follow all requirements for the GraphQL over HTTP spec.

from pioneer.