Alec Aivazis

Since we now have a place to park prompt-level configuration, we should clean up how we provide stdio internally

Support SvelteKit's new API

3

This PR updates houdini's APIs to be compatible with the updates to SvelteKit as described here: https://github.com/sveltejs/kit/discussions/5774. Unfortunately, I won't be able to get the integration tests to pass until...

Infer inline query variables from route parameters

2

If a route's path contains parameters that match a query's variables, the user shouldn't have to define a variable function if its just going to do `({params}) => params`. Questions:...

Preprocessor with external files

5

At the moment, if a user wants to use the preprocessor to generate a load function they must define their queries inline and use the appropriate "inline" function for the...

Add way to toggle between isolated and global stores

2

In order to support situations where a user wants to SSR a component query (or for some other reason interact with a store), we need to support a distinction between...

Imperative cache API

2

Houdini needs to provide the user a way to interact with the cache imperatively to handle situations that aren't covered by the declarative API

There are a few things that are missing from the integration tests: - [ ] CachePolicy logic - [x] Subscribe and Unsubscribe on route transitions - [ ] pending load...

Refetchable fragments

2

There should be a `@refetchable` directive that labels fragments on `Node` or `Query` as refetchable. The api could look something like this: ```javascript const { data, refetch, variables } =...

There are a few places where we could really use better error messaging that suggest fixes or link to the docs.: - [ ] mising `__typename` in abstract optimistic responses...

Optimistic Fetches

3

The computation for partial data relies on running into a field we've already seen before. We should be able to provide a hint to the cache when looking up the...