Jordan Eldredge

@Rash-Hit Following up here. Are you still interested in working on this? No worries if not.

@Rash-Hit Yeah, that looks about right. We probably also need to check that it's `as const` (look at the `.identifier` of the as expression. You'll also need to make sure...

Closed in https://github.com/captbaritone/grats/pull/137

Did some research and found a few leads: 1. https://github.com/microsoft/TypeScript/pull/20234 2. https://github.com/vlcn-io/typed-sql/blob/main/packages/cli/src/Analyzer.ts#L102 3. https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API#writing-an-incremental-program-watcher 4. Using the Language Service API · microsoft/TypeScript Wiki · GitHub https://github.com/microsoft/TypeScript/wiki/Using-the-Language-Service-API

The most promising looking thing so far is these two methods on `ts.LanguageServiceHost`: 1. `.getProjectVersion()` 2. `.getScriptVersion()` I suspect these will let me track changes more incrementally.

https://github.com/vlcn-io/typed-sql/blob/main/packages/cli/src/Analyzer.ts

After some discussion in other issues (https://github.com/captbaritone/grats/issues/21#issuecomment-1790899490) and on Discord, I think this is probably not great to use positional arguments. GraphQL arguments are named/keyed so, while the object syntax...

Another point in favor of this approach is the ergonomics of default values, especially when combined with descriptions. ```typescript /** @gqlField */ export async function searchItems( _: Query, { query,...

Another argument in favor of this approach came up in Discord and I figured I'd document it here: One appealing pattern which is uniquely enabled by implementation first solutions like...

As I think more about this, one of the key value Grats unlocks, is to expose _existing_ methods as fields. I think enabling that type of developer experience might bring...