Marshall Cottrell

> And have the LINQ provider automatically pick up and recognize attributes and add `.OptArg("index", "lastname_ix")` to the underlying query terms appropriately. @bchavez to add to this, in `thinky` I...

Note the build failures already existed on `master` and are not a result of this change.

@vilic I just pushed up another commit addressing the remaining cases in `help.ts`. Could still use some direction on testing. I can't really tell how the generator works. Perhaps it...

@vilic no problem, just let me know if you need anything else! Cheers!

@ajafff good call on using `require.resolve`, just updated this PR to do so. Note I rebased on top of 0e075f1 to get rid of those test failures. The existing (JS-based)...

Another interesting case/need we've come across is the ability to build `where` clauses based on FK information contained in a single generic `ID` parameter. This would not be possible to...

After thinking about it a bit more, we could maybe implement this in the plugin that handles `Connection.conditions` query filtering. It could add the generic `nodeId` parameter (hopefully with a...

@benjie another option would be (for use in custom functions) require the user to create a custom type for the given table that contains only and all elements of the...

Related to #1074 in that Voyager is probably closer to what you'd want to expose to end-users instead of the entire GraphiQL console.

@philipaconrad it would also be convenient to expose a builtin for fetching the GraphQL schema from a remote endpoint. If you are already using the new built-ins I'm curious how...