Improved type generation, and automatic graphql query/mutation strings

[SorenHolstHansen]

Improved type generation, and automatic graphql query/mutation strings

[AlecAivazis]

Hey @SorenHolstHansen - thanks for opening this up. Let me try to unpack it a bit.

One of the key designs in houdini is that related stuff should be colocated with your component. When query documents are split up from their components, users are naturally encouraged to think about their queries being shared in ways that aren't tied to their component hierarchy. In my experience (primarily with Relay) it's very important to keep things compartmentalized. When codebases get large, the constant bouncing back and forth between different files can be tiresome. It Also, I'm not sure I understand the difference between adding your query body in a separate .gql file vs your component body. As long as queries and fragments stay focused they shouldn't get large enough to warrant the extra file, imo.

Probably worth mentioning that you can use the --pull-schema or just -p in order to pull down the most recent schema before generating. This means that you really only have to ever define the schema on the server as the source of truth, and then use it in your component

[SorenHolstHansen]

Cool, I didn't know about the --pull-schema option, definitely makes it a lot nicer.

[ohmree]

Also, I'm not sure I understand the difference between adding your query body in a separate .gql file vs your component body. As long as queries and fragments stay focused they shouldn't get large enough to warrant the extra file, imo.

One such difference is syntax highlighting - the graphql snippet in the sample from the readme isn't highlighted for me in emacs with web-mode and adding support would be a pain.

Also I haven't checked this, but if svelte's language tools don't integrate with tsserver plugins such as ts-graphql-plugin then intellisense is another issue that would be solved by allowing graphql in separate files.

EDIT: seems like this might've been fixed in web-mode, I'm just trying to figure out how to enable it and/or if it's sufficient for me.
Still, this could all be avoided if I could just use the standard tooling for graphql files (which would require houdini to support separate .gql files).
EDIT 2: yeah I don't think the fix for the aforementioned issue does anything to syntax highlighting.
So the only way I could use houdini with reasonable DX would be if support for separate .gql files was added.