useQuery tracked properties proxy?

[brave forum]

Default react-query uses a proxy-like setup to only re-render useQuery when one of the accessed properties are updated. Eg. Doing:

const { isLoading } = useQuery(...)

makes it so it only re-renders when isLoading changes. Blitz RPC breaks this behavior due to it accessing everything with a spread and returning it later. Is this something that we can fix? It makes for an awful lot of unnecessary re-renders

[toxic surge]

Hey @brave forum, would you mind making an issue for this in github?

I don't have an answer to fix this right now, but will try looking into this.

[brave forum]

Is there a way to change the useQuery TS source when forking Blitz while still being able to use it in a test project? I can take a look at it

[toxic surge]

I don't think I follow, what you mean change the ts source?

[brave forum]

Well, I tried to see if I can make it work by changing the node_modules source but the compiled code is so hard to follow that I cant really debug issues. So i was wondering if the test projects inside the Blitz source code allow me to change the actual source code while testing/working on it or if I have to change => compile => debug etc

[toxic surge]

Hey you will need to change the required code and then pnpm build in the root folder to compile the code.

In short just fork the repo, clone it and then run pnpm i followed by pnpm build to initially compile, then make you changes in packages/blitz-rpc.

You can use the apps/toolkit-app to test or you can use pnpm link to test in your existing app.

You can also use pnpm dev to setup the dev watch of each file change so that you don't need to keep running pnpm build

Do let me know if you face any trouble setting it up locally.

[brave forum]

Do you happen to know if this idle status check is required? https://github.com/blitz-js/blitz/blob/82551729407014e6dc4dce50da8add2e44088161/packages/blitz-rpc/src/query/react-query/react-query.ts#L194C5-L194C37