Fix: Set urql client requestPolicy to network-only to prevent stale data #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
You were experiencing out-of-date views due to the default caching behavior of the urql GraphQL client (
cacheExchange).This change modifies the client initialization in
src/app/api/utils.tsto use thenetwork-onlyrequest policy. This ensures that all GraphQL queries made through this client bypass its cache and fetch fresh data from the network, resolving the stale data issue.Manual testing is recommended to confirm the fix and check for any performance implications.