fix: chatters request bypass cache #68
Merged
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.
✨
Description by Callstackai
This PR introduces a fix to the chatters request by adding a fetch policy parameter to the GraphQL query method in the Twitch API, allowing for more control over caching behavior.
Diagrams of code changes
sequenceDiagram participant ChattersModule participant TwitchApi participant ApolloClient ChattersModule->>TwitchApi: gql<ChattersResponse>(ChattersQuery, {name: login}, "network-only") TwitchApi->>TwitchApi: getApolloClient() TwitchApi->>ApolloClient: query(gql query, variables, fetchPolicy) ApolloClient-->>TwitchApi: GQLResponse<T> TwitchApi-->>ChattersModule: {data} ChattersModule->>ChattersModule: Update chatter counter ChattersModule->>ChattersModule: Log info messageFiles Changed