solid-query - have same api as vue-query, to lessen maintenance

[birkskyum]

I think the choice of using create (createQuery) over use (useQuery) exclusively for solid isn't as important as keeping the solid-query package synched̉ with changes in the vue-query version, and that might be easier if the api is the same.

[TkDodo]

right now, we have:

• react: useQuery
• vue: useQuery
• solid: createQuery
• svelte: createQuery
• angular: injectQuery

I think sticking to a naming convention that aligns with how each framework tends to name things is fine. For React, that’s clearly use because of the rules-of-hooks.

[birkskyum]

This is what it would look like:

• fix(solid-query): add useQuery, useInfiniteQuery, useQueries, useMutation as alternative (primary) syntax to align with react and ease maintenance #8938

Makes is possible to just copy/rename a react-query folder to solid-query, and have the diff at a glance with git, with backwards compat to the createQuery etc

[TkDodo]

okay so you want this internally, but not as an external facing API ?

[birkskyum]

external facing too, but we can leave an alias to the few create functions to not break any user code. There aren't docs for most of the solid query API, like useMutation, so users have to rely on the react docs and figure out the rest, and it's a lot easier the closer the API surface is.

[TkDodo]

external facing too

I’m really not sure about this, but it’s for the solid community to decide. solid has createSignal and createEffect, I’m not sure how other libs do it but it seems create... is the standard

I can see that right now, both are exported (use... and create...) which is fine but we might want to deprecate one and settle on the other to move to that in the next major

[birkskyum]

it's really a mix of make, create, use for solid users. The official solid-router, which is in virtually all solid-app has a use-syntax consistently.

Everyone in solid just want libraries that work, and we generally have much bigger fish to fry that naming. Being a small community means companies aren't too keen on helping out with maintenance of SDKs for anything, so we have to take the opportunities that exist to lessen the maintenance burden for solid libraries.

[Thiagolino8]

that might be easier if the api is the same

The APIs, despite being analogous, are still different, createQuery receives a function that returns an object instead of the object directly
And now that the Svelte version is changing to use signals with the same format as the Solid one, I believe it makes sense to keep the create prefix of both for distinction.

[birkskyum]

I agree that there could be a larger api overlap between solid/svelte/vue contra react - but vue also use signals (refs), and it has the use syntax with a much higher adoption, so i'm trying to lean in that direction. Also, as svelte moves to runes, the create syntax appear to become the odd-one-out - e.g. https://userunes.com/, and similar to solid could arguably benefit from just aligning on use with vue/react.

[TkDodo]

i don't see why it was made with create in the first place, given e.g. https://userunes.com/

because it was made before runes existed, and svelte5 compatibility is still being worked on

[birkskyum]

Ah, of course - i thought svelte also used use before that, but can see svelte 4 was move on the create or no-keyword style