Daniel Rearden

We could add `@graphql-tools/module-loader` to support loading schemas using `module:someModule#identifier` syntax. The existing loaders should however already be able to pick up a file like this: ``` schema: './node_modules/@foo/graphql-schema/schema/schema.graphql' ```

You may want to take a look at [graphql-middleware](https://github.com/prisma/graphql-middleware). Middleware functions let you hook into the resolver before and after it fires. The lib is fully compatible with `neo4j-graphql-js` --...

Initial pass available in [this branch](https://github.com/danielrearden/sqlmancer/tree/annotations).

That is working as intended, although it may not be well documented. If you have any columns you want to *always* select, you can specify them using the `include` argument...

@TSiege Sorry, I think I misread your original post. If field `x` includes `@depend(on: "y")`, then the resolver for `x` should be able to access the value for column `y`...

@TSiege Thanks for the bug report. This does appear to be an issue with the type definitions, but I'm not able to reproduce it on my end. Do you think...

Thanks, that's super helpful. I'll investigate what can be done on this side to prevent those sort of errors.

@zth Thanks for the above input. I think your suggested approach is very reasonable and wouldn't be too difficult to implement. If we were to use a directive, I think...

Hi @unlight Thanks for the bug report. The directives included in `schemaDirectives` will not include all possible directives -- only the ones that actually transform the schema as opposed to...

I'm not that familiar with NestJS, but I believe if you provide both `typePaths` and `typeDefs`, the resulting type definitions should be merged together. So you should be able to...