Luke Morales

I'm asking because it really seems to me that this structure should fit your needs: ```ts const store = createQueryKeyStore({ customers: { listByAccountId: (accountId: number, queryFilter: QueryFilter) => [accountId, 'list',...

@kimbuba oh, that's definitely a use case not supported yet. Do you have more examples of similar use cases?

> that would be to support a hierarchy structure. Basically scoping some keys to an entity ID, or any other use cases? I remember thinking something like this when designing...

Thanks for the information @kimbuba, I'll start some exploration towards that use case

@kimbuba just letting you know, v1.0 has been released with support for nested keys: https://github.com/lukemorales/query-key-factory/releases/tag/v1.0.0

Just changed the title because I was able to see state updates happening on nested routes, and the root loading also updating if my App entry point was a nested...

> new QueryClient is theoretically irrelevant to react. Incorrect, React Query's QueryClient uses React Context, so if you try to create a new instance on the server, it will throw...

Packages that rely on any type of context need to be called on the client. For it to work you'll need to create separate components or make your `app/page.tsx` a...

It seems that the repro is missing the `app` directory, perhaps it's breaking because by enabling the feature, Next makes `app` the root directory and if you don't have the...

If your reproduction matches exactly your setup, you need to add `app/layout.tsx` for that to work. Once you enable the app directory next is gonna use that as the root,...