[bug] caching issues on profile page and hypercert view page

[holkexyz]

• There is a caching issue at least for the marketplace "bought" tab and the hypercert "owned" tab: https://www.loom.com/share/259438ca67ba41aa99abb0e4f0ffccc0?sid=345418e4-107e-4d84-8cce-b393e185f441
• And one for the ownership table on the hypercert view page: https://www.loom.com/share/af851c142bec4284bec569a73c8bd71a?sid=6d5bc05e-5fa6-4fbd-a720-96a6d643a7e8

[Jipperism]

Struggling to reproduce this locally, with a production build on main branch. It does reproduce for me on https://app.hypercerts.org/profile/0x617B7ab789bafF8B7c4d641d18e2fc42d1e1666e?tab=marketplace-listings, as is shown in the video. Need to refresh the collections page, and then the counts are incorrect when navigating to the marketplace tab. However they're correct when running the app locally. Purging the nextjs cache doesnt help either.

EDIT: Resetting the hypercerts api doesn't solve the problem either. already expected it wouldn't just putting it here for other people trying to reproduce.

[bitbeckers]

For the first issue:

I think we should implement the structure implemented in #420 onto the marketplace tabs as well

For the second issue:

We should implement that pattern for the HypercertDetailsComponent (I think it already is) and make sure to trigger the invalidation of the cache on Split, Transfer, Merge, Burn, Claim transactions - when succesful.

[Jipperism]

@bitbeckers I feel like those invalidations could possible be triggered by the indexer maybe? or some other event watcher? that at least solves the problem of people closing their window before the invalidation gets triggered.

[Jipperism]

@bitbeckers I'm dizzy/stale on where we stand with this issue after our meeting this morning. Feel like this has a good chance of becoming a permanent column inhabitant until we reach consensus on next steps wrt the caching problem?

[bitbeckers]

I'm dizzy/stale on where we stand with this issue after our meeting this morning

Why? We'd opt for server side data fetching and generation, no? I need to wrap up the PR but didn't get around to this.

Is anything else unclear?

[Jipperism]

@bitbeckers Should we assign this issue to you then? Or revisit once the PR gets wrapped up?