Kim di centa le van kim
Kim di centa le van kim
Hello Luke! Yes sure. I need to support the following keys structure ["customerListByAccountId", accountId, 'list', {orderBy:"create_date"}] ["customerListByAccountId", accountId, 'list', {orderBy:"id"}] ["customerListByAccountId", accountId, 'list2', {orderBy:"create_date"}] how do i clean this using...
thanks, i see. Would it be possible to go more deeper in the hierarchy? Say: customer/10/stakeholders/213/load that would easily translate into [customer,10,stakeholders,213,load] so i could easily invalidate customerId 10 and...
that would be to support a hierarchy structure. But i'm trying to adapt my current structure to your library. Btw is this queryClient.invalidateQueries([...store.customers.accountId._def, accountId], { refetchActive: false }); actually queryClient.invalidateQueries([...store.customers....
np, here is another example: I have a list of accounts and each account has customers i want to do different lists per customers, as they are calling different endpoints....
@xuzuxing thank you! I'll try to have a look, hopefully in the next days. Thank you!
You can change this behavior by setting emit_empty_slices to true.