[issues/66] Backup unlinking when opened

[rough prairie]

alchemistie

Issue opened (#66) - Backup unlinking when opened

When I open a saved backup in discohook, it seems to unlink immediately, here's a video.
What usually occurs, and what i expect, is the backup of a message to automatically stay linked to its associated backup.

The issue doesn't seem to occur on the majority of my backups, but for some reason one in particular has it. Here's a safe share link of the message in question if it may be helpful or relevant.

discohook/discohook

[rough prairie]

shayypy

[discohook/discohook] New comment on issue #66: Backup unlinking when opened

Looks to be more of an issue with the modal loading backup metadata since obviously the page is aware it has opened a backup. It may even still autosave. Will try to repro on my own

[rough prairie]

shayypy

[discohook/discohook] Issue closed: #66 Backup unlinking when opened

shayypy

[discohook/discohook] New comment on issue #66: Backup unlinking when opened

Unfortunately I can't get this to happen with any of my backups either in local or prod. Something may have changed between september and now. Given how far down you are in the list at the start of the video, it may also have been an issue with pagination, but I'm not sure (it would depend on how many backups you have)

@alchemistie can you still reproduce this issue?

[rough prairie]

alchemistie

[discohook/discohook] New comment on issue #66: Backup unlinking when opened

@alchemistie can you still reproduce this issue?
I haven't seemed to have this issue after that incident, you're right that it might have fixed itself with other updates. I will let you know if it occurs again, but hopefully this means it's a solved problem. Thank you for your response!

[rough prairie]

shayypy

[discohook/discohook] Issue reopened: #66 Backup unlinking when opened

shayypy

[discohook/discohook] New comment on issue #66: Backup unlinking when opened

It turns out this was not fixed, but I identified the problem, so I'm going to re-open this so I can close it as fixed in an upcoming commit.