houdini
houdini copied to clipboard
The disappearing GraphQL client
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...
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically....
### Describe the feature Due to reasons I need a custom `build.js` script that calls vite's `build()`, patches some files, moves the output to its target destination and creates a...
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:...
Demo: https://github.com/janvotava/houdini-error-reproduce-001 When the `$GQL` store is read in the [__layout.svelte](https://github.com/janvotava/houdini-error-reproduce-001/blob/main/src/routes/__layout.svelte#L12), the resulting data in the [routes/index.svelte](https://github.com/janvotava/houdini-error-reproduce-001/blob/main/src/routes/index.svelte#L21) will be `null` for some reason and SSR won't work.
additionally, customizing `GQL_` would be nice, some projects have case conventions. _Originally posted by @endigma in https://github.com/HoudiniGraphql/houdini/issues/391#issuecomment-1206668510_
I'm currently reading https://www.houdinigraphql.com/api/config and I can't seem to find the field that changes the path or name of the ``$houdini`` folder.
The following happens when I call loadNextPage on the Query Store and my query has variable limit and is not written by default (otherwise it's working correctly): 1. First request...
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...
With the store api lazy queries are now easily possible by defining them in a separate file. But I would love to be able to define them inline. My idea...