79a093eb28
## Issue Ticket: 108 ## Interesting Uploads Page uses `claim_list` Channel Page uses `claim_search A second `claim_list` would instantly show updated results, but `claim_search` takes a long while to reflect the deletion. ## Change This PR only handles the `claim_list` (Uploads Page). The `claim_search` version would be troublesome to handle. If a refresh would bring back the results (due to the `claim_search` slow update behavior), we would need to store the deleted claim persistently. Then ... - Store where? rehydrate? - When to clear? - How to make each `ClaimList` filter this out without polluting the code? etc. ...will be messy. Feels easier to "fix" at the `claim_search` level to make it update faster (maybe a command to clear cache at server or something). |
||
---|---|---|
.. | ||
app.js | ||
blocked.js | ||
claims.js | ||
coinSwap.js | ||
collections.js | ||
comments.js | ||
content.js | ||
file_info.js | ||
livestream.js | ||
notifications.js | ||
publish.js | ||
reactions.js | ||
reportContent.js | ||
rewards.js | ||
search.js | ||
settings.js | ||
subscriptions.js | ||
sync.js | ||
tags.js | ||
user.js | ||
wallet.js |