Fix docs on calling queries and actions on the server about wasp HOT 3 OPEN

They can also import action directly, from its file. In which case they have to construct the context completely on their own, while allegedly, if they import it via wasp/server/operations, they don't have to construct it completely on their own, but need to pass just user to the context and rest will be added.
We should confirm this and decide if we want to document "raw" import approach also or not.

from wasp.

@Martinsos I'm not sure I follow how to call queries without the useQuery hook.

From the docs I had initially understood that wasp would magically add the context, even when calling the function without the hook. Per your last comment, that is not the case, though, and I'm still confused on how to actually do it.

It seems that to directly call the query I must pass the query cache key, plus the user (as context). The advanced usage section for actions says we can get the queryCacheKey from the "operation" itself, but that doesn't work:

import { getTasks } from 'wasp/client/operations';

// ...

const { data: tasks } = await getTasks(getTasks.queryCacheKey, { user });

I would suggest adding to the docs an example of how to call queries with entities without the useQuery hook. I would also say the concepts valid for both queries and actions could be in a separate section that appears before queries and actions, perhaps directly in Overview.

edit: opened a question in discord too.

from wasp.

@leoschet As mentioned on Discord, this issue deals with calling Operations from the server, so it's not really applicable to your situation.

However, the advanced usage docs you linked do talk about calling Operations from client, and you've successfully caught two mistakes. I've created an issue for fixing the docs and improving the API: #1923

Thanks!

from wasp.