react-query useQuery inside a provider with with dynamic parameters

Question

I'm using react query because it's super powerful but I'm struggling trying to share my data across many components inside a provider. I'm wondering if this is the right approach.

PostsContext.js

import React, {useState} from 'react';
import { useTemplate } from '../hooks';

export const PostsContext = React.createContext({});

export const PostsProvider = ({ children }) => {
    const fetchTemplate = useTemplate(templateId);
   
    const context = {
        fetchTemplate,
    };

    return <PostsContext.Provider value={context}>{children}</PostsContext.Provider>;
};

useTemplate.js

import React from 'react';
import { useQuery } from 'react-query'
import { getTemplateApi } from "../api";

export default function useTemplate(templateId) {
    return useQuery(["templateId", templateId], () => getTemplateApi(templateId), {
        initialData: [],
        enabled:false,
    });
}

and then my component that uses the context

function Posts () {
    const { fetchTemplate } = useContext(PostsContext);

    console.log(fetchTemplate.isLoading)

    fetchTemplate.refetch() <---- how can I refetch with a different templateId?

    return {...}

}

I'm looking for a way to dynamically call my hook with a different templateId but with the hook inside the provider so I can use it all over my app. Is this the right approach? I have deeply nested components that I don't want to prop drill.

TkDodo · Accepted Answer · 2021-02-13 06:58:43Z

13

You don’t need an extra way to distribute your data, like react context. Just call useQuery with the same key wherever you need to, and react query will do the rest. It is best to abstract that away in a custom hook.

refetch should only be used if you want to refetch with the exact same parameters. For changing parameters, it’s best to. make them part of your query key, because react query will refetch whenever the query key changes.

So in your example, you only need to call useTemplate with a different templateId. templateId itself is local state (which template has been selected by the user or so), and how you make that globally available is up to you.

answered Feb 13, 2021 at 6:58

TkDodo

30.4k5 gold badges84 silver badges99 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Garuuk Over a year ago

I get that but what if I have a getTemplates call at the parent level. And I want all my children to have access to the data that this getTemplate call makes. Would I want to store the data property from the query call in a global property like a provider instead of storing the hook itself? I see what you're saying.

TkDodo Over a year ago

No, you would just call useQuery in the child again, and react-query will give you the data from the cache.

Garuuk Over a year ago

I see. Because it's the same query key it caches the query based off the query key and you can adjust the cache properties. This helps a lot thank you!

TkDodo Over a year ago

Yes, that’s exactly the idea. And custom hooks help in abstracting that away, which makes it a breeze to work with :)

Collectives™ on Stack Overflow

react-query useQuery inside a provider with with dynamic parameters

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related