Closed atasoya closed 4 days ago
@atasoya thank you for the report, I've assigned myself to test this out and see what's going on.
Yep, it seems that our implementation currently doesn't support passing arguments to the CRUD override function for getAll
on the client.
The implementation should be improved to make sure the tasksCrud.useQuery
is working in the same way as useQuery
.
One temporary workaround (temporary because we will fix this) is to use the useQuery
helper with the CRUD query directly like this:
import { tasks as tasksCrud } from 'wasp/client/crud'
import { useQuery } from 'wasp/client/operations'
const { data: tasks, isLoading } = useQuery(tasksCrud.getAll.query, {
filter: 'my search',
})
Describe the bug When getAll query is overrode and custom logic requires arguments from client, wasp doesn't let to provide arguments.
To Reproduce Steps to reproduce the behavior:
Expected behavior Let argument passed from client.