Daniel Rearden
Daniel Rearden
Optional arguments and parameters should not use the maybe type except where passing in a null value is semantically different from passing in an undefined value. So ``` operationName?: ?string...
With SDL [officially](https://github.com/graphql/graphql-spec/pull/90) part of the specification, would it be worthwhile to provide a way to build a build a fully-featured schema from a Document AST? Currently, schemas built using...
I'm opening this issue so we can further discuss approaches to A) splitting the middleware into separate functions and B) supporting additional frameworks. Here are some initial thoughts: **Goals** *...
Users should be able to have mock data returned instead of making any database calls. This would not only enable users to stub out individual fields, but could be helpful...
There’s a number of issues with the library in its current form: * Reliance on schema directives means the library is incompatible with code-first libraries like `nexus`, `type-graphql` or `graphql-compose`...
There's a number of naming conventions that could potentially be made configurable: - Argument names like `where`, `orderBy`, `limit` and `offset` - Logical operator field names like `and`, `or` and...
Sqlmancer should provide a way to enforce maximum values when calling the `limit` method, as well as a default limit value that could be set if the method is never...
The `@sqlmancer` directive could accept a list configuration objects instead of just one, allowing the generation of multiple database clients. This would be useful for projects that utilize more than...
The library currently makes use of schema directives for both transforming the schema and providing metadata about the underlying database. This works well enough, but will make it difficult to...
It would be feasible to automatically publish an event when an insert, update or delete operation takes place, potentially reducing the boilerplate required to set up subscriptions. A PubSub implementation...