✨ Add search page #207
✨ Add search page #207
Conversation
arcalinea
temporarily deployed
to
search-content - ozone-staging PR #207
Render
Destroyed
| const searchInfo = useInfiniteQuery({ | ||
| queryKey: ['searchContent', { term, section }], | ||
| enabled: !!term, | ||
| queryFn: async ({ pageParam }) => { | ||
| const { data } = await labelerAgent.app.bsky.feed.searchPosts({ | ||
| q: term, | ||
| limit: 30, | ||
| sort: section, | ||
| cursor: pageParam, | ||
| }) | ||
| return data | ||
| }, | ||
| getNextPageParam: (lastPage) => lastPage.cursor, | ||
| }) |
There was a problem hiding this comment.
I fear that this query could have two effects:
- a lot of entries end up being cached, significantly increasing the memory usage
- there isn't any mechanism to clear that cache so the user could end-up seeing stale results when trying to search for newer posts.
Is there a way to invalidate all searchContent cache entries, for example when the component gets destroyed ?
Alternatively, maybe a mutation would be more appropriate here ? (The browser's HTTP cache would provide the short term caching)
There was a problem hiding this comment.
good point but I think this is actually what we want. when investigating search results, I don't think a 5m delay in seeing realtime content is a big issue for mods and in fact, we wouldn't want the results to change while they are scanning a specific page for a keyword so overall, the caching seems to be a good idea.
keep in mind that at any given moment, a mod will probably scan for only a few keywords so keyword specific caches can be kept around without overwhelming memory usage IMO.
This PR adds a dedicated page to show top and latest posts for a search keyword which surfaces the same content as the app. This helps moderators to quickly find and proactively action content without having to go through the app.