Jordan Eldredge

I've been having the same problem, although I see a slightly different pain-point and expected result. For me the frustration comes from the fact that after I type "true", if...

> In a world where we'd want to ideally eliminate all updaters, optimistic updates will need to be handled by the local data-store layer. Would this become entirely a concern...

> I was actually thinking about doing a little experiment implementing a Network layer fetchQuery that doesn't really fetch over HTTP, but gets data from local SQLite. I did a...

> I also looked at Relay resolvers, but they work so differently to normal resolvers... tied to fragments instead of the schema itself. Sorry for the confusion. We've been expanding...

@Lalitha-Iyer > Would this mean we would continue to use client state management libraries like Redux but provide a common abstraction for querying? Correct. You could continue to use Redux...

@ivosabev When we first started looking at the problem, that's what we thought as well! But it turns out that while technically Client Schema Extensions could be used to model...

Replaced by #149

## Sketch of inlay hints ```ts proxy.provideInlayHints = (fileName, range, context) => { const prior = info.languageService.provideInlayHints( fileName, range, context, ); const doc = info.languageService.getProgram()?.getSourceFile(fileName); if (doc == null) return...

## Sketch of code actions ```ts proxy.getCodeFixesAtPosition = ( fileName: string, start: number, end: number, errorCodes: readonly number[], formatOptions: TS.FormatCodeSettings, preferences: TS.UserPreferences, ): readonly TS.CodeFixAction[] => { const prior =...

@Rash-Hit Sorry I missed your message! I think all we need to do here is update the code [here](https://github.com/captbaritone/grats/blob/2f7323fb43a31ed1895b394bbdbc01fba583cc0c/src/Extractor.ts#L719) to expect an "AsExpression" with an expression that is the expected...