webtau
webtau copied to clipboard
GraphQL DSL - configurability
- url - in theory it's possible someone may serve at root for example, rather than graphql. It's debatable whether we should do this at all or just force users to stick the graphql path in the base url config.
- success status code - in case people deviate from best practices
- invocation method - there are many ways to invoke a graphql service according to best practices: POST bodies like I've used, GET and query params and POST with application/graphql content type. We probably should allow any of these.
on (1), sticking with the standard /graphql path is at the very least a sensible default. Should be easy to make configurable if we hear that it's a limiting factor for a potential webtau user. Compared to (2) and (3), this seems like a very low priority.
I think in general this whole issue is low priority compared to some of the other issues in https://github.com/testingisdocumenting/webtau/projects/4.
closing as no active