Skip to content

Clarified context passing for queries when used from server #3153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 2, 2025
Merged

Clarified context passing for queries when used from server #3153

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aeeb941
Clarified context passing for queries when used from server
Martinsos Sep 13, 2025
3993402
fix
Martinsos Oct 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion web/docs/data-model/operations/queries.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -271,7 +271,8 @@ Calling a Query on the server is similar to calling it on the client.
Here's what you have to do differently:

- Import Queries from `wasp/server/operations` instead of `wasp/client/operations`.
- Make sure you pass in a context object with the user to authenticated Queries.
- Make sure you pass in a `context` object with the `user` field to authenticated Queries.
- Note that you don't have to pass other parts of the `context` object, like Entities, those will get injected automatically.

<Tabs groupId="js-ts">
<TabItem value="js" label="JavaScript">
Expand Down
Loading