content-watcher should find any Replies on chain and announce them to the backend. However, when the backend receives the announcement, the replies may not be correctly stored in the db cache, and therefore not displayed in the feeds.
I think there must be a difference in the code path for storing content from the initial scan and the ongoing end-of-chain scan.
Debugging Notes
social-app-template-backend implemented a cache for post data, and Replies do not display in the feed because the cache is not properly invalidated. Cache items that have replies need to be refreshed in order to display them correctly.
Acceptance Criteria
[ ] content-watcher finds replies in real-time and the social-app-template-backend and social-app-template-frontend are able to display the replies correctly nested in the feeds.
Description
content-watchershould find any Replies on chain and announce them to the backend. However, when the backend receives the announcement, the replies may not be correctly stored in the db cache, and therefore not displayed in the feeds.I think there must be a difference in the code path for storing content from the initial scan and the ongoing end-of-chain scan.
Debugging Notes
social-app-template-backendimplemented a cache for post data, and Replies do not display in the feed because the cache is not properly invalidated. Cache items that have replies need to be refreshed in order to display them correctly.Acceptance Criteria
content-watcherfinds replies in real-time and thesocial-app-template-backendandsocial-app-template-frontendare able to display the replies correctly nested in the feeds.