Closed ugur-eren closed 4 months ago
Name | Link |
---|---|
Latest commit | 1ab99de7b07d75af26e0804f0a2a26903eac1c9f |
Latest deploy log | https://app.netlify.com/sites/starknet-react/deploys/6632363e0d28e1000823f1eb |
Deploy Preview | https://deploy-preview-437--starknet-react.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Good catch, thank you!
The current implementation of the query client within the function component leads to the creation of a new query client on each re-render. Consequently, this behavior results in the loss of data and caches associated with the query client.
This PR addresses the issue by relocating the default query client outside of the function component. By doing so, we ensure that the query client persists across re-renders, maintaining data integrity and cache consistency.
While it's possible to resolve this issue by directly providing the query client to the Provider on usage, this caused us some time to locate and fix the issue, hence the decision to refactor the implementation.