TanStack•14mo ago•

10 replies

living-lavender

useQuery to get data in nested route

I've been using

useQuery

useQuery

without a queryFn but say query key to get the data and status information about the query in a components outside where I supply the queryFn [I thought this was supported behavior, let me know if it isn't]. If I have a path like

reports/$reportId

reports/$reportId

I have the

useQuery

useQuery

with the queryFn at the "reports" level, but then

useQuery

useQuery

without queryFn at the "$reportId" level. When I navigate from

/reports

/reports

/reports/$reportId

/reports/$reportId

this all works fine, but if I go directly to

/reports/$reportId

/reports/$reportId

the queryFn is never called. If I avoid rendering the outlet in

/reports

/reports

until after the query is finished it does work. Is this expect? Is there a way to do this without the conditional rendering of the outlet? Is there another setup that is more correct?

TanStack•14mo ago•

10 replies

living-lavender

useQuery to get data in nested route

I've been using

useQuery

useQuery

reports/$reportId

reports/$reportId

I have the

useQuery

useQuery

with the queryFn at the "reports" level, but then

useQuery

useQuery

without queryFn at the "$reportId" level. When I navigate from

/reports

/reports

/reports/$reportId

/reports/$reportId

this all works fine, but if I go directly to

/reports/$reportId

/reports/$reportId

the queryFn is never called. If I avoid rendering the outlet in

/reports

/reports

until after the query is finished it does work. Is this expect? Is there a way to do this without the conditional rendering of the outlet? Is there another setup that is more correct?

useQuery to get data in nested route

Similar Threads

useQuery to get data in nested route

Similar Threads

Similar Threads

Similar Threads