fix: invalidate content preference from tag and source #4087
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
capJavert
requested review from
rebelchris,
omBratteng,
ilasw,
sshanzel,
nensidosari and
AmarTrebinjac
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
capJavert
commented
Jan 20, 2025
Comment on lines
+128
to
+131
| invalidateContentPreferences({ | ||
| entity: ContentPreferenceType.Keyword, | ||
| subQuery: RequestKey.UserFollowing, | ||
| }); |
There was a problem hiding this comment.
Create new function without debounce since invalidation happens for different queries then the ones shown.
There was a problem hiding this comment.
Debounce also does not support function having args
AmarTrebinjac
approved these changes
Jan 20, 2025
rebelchris
approved these changes
Jan 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
Since new feed settings are using content preference queries we want to invalidate specific queries for source/tag block/follow so visiting feed settings correctly refetches data.
Events
Did you introduce any new tracking events?
Experiment
Did you introduce any new experiments?
Manual Testing
Caution
Please make sure existing components are not breaking/affected by this PR
Preview domain
https://as-915-invalidation-tag-source.preview.app.daily.dev