mirror of
https://github.com/BoostIO/BoostNote-App.git
synced 2026-04-27 05:15:56 +03:00
[GH-ISSUE #427] Db recovery tool #199
Labels
No labels
android 🤖
assigned to core 🦹
bug 🐛
documentation 📚
documentation 📚
duplicate 🚫
external issue 🔼
external issue 🔼
feature request 🌟
funded on issuehunt 💵
help wanted 🆘
improvement request 🔨
improvement request 🔨
ios 🍎
mobile 📱
needs investigation 🔬
needs more info ℹ️
needs specs 📐
plugin idea 🔌
plugin idea 🔌
poll 🗳️
pull-request
question ❓
rewarded on issuehunt 🎁
security issue 🔑
won’t fix ❌
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/BoostNote-App#199
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Rokt33r on GitHub (Apr 23, 2020).
Original GitHub issue: https://github.com/BoostIO/BoostNote-App/issues/427
Current behavior
Storages are gone after updating because of some reasons.
https://github.com/BoostIO/BoostNote.next/issues/380
https://github.com/BoostIO/BoostNote.next/issues/414
https://github.com/BoostIO/BoostNote.next/issues/418
I'm assuming this problem is storage bugs in v0.2.0 so it shouldn't happen anymore.
The current solution is this.
https://github.com/BoostIO/BoostNote.next/issues/380#issuecomment-608569928
Expected behavior
Introduce some recovery UI so users can do the same solution in https://github.com/BoostIO/BoostNote.next/issues/380#issuecomment-608569928 without opening console of electron or browser.
@arcturus140 commented on GitHub (Apr 24, 2020):
@Rokt33r can you please clarify, is storage removal a destructive operation? the warning message says it is being unlinked.
@arcturus140 commented on GitHub (Apr 24, 2020):
I am referring to normal user operation, unrelated to bugs.
@Rokt33r commented on GitHub (Apr 25, 2020):
@arcturus140 Sorry for making you confused. I might need to change the warning message to give a clear idea.
The operation is destructive. It discard storage data from the app(or browser) but not cloud storage data. If the storage is linked to a cloud storage and synced before deleted, you can always revive the storage from the cloud storage.
@arcturus140 commented on GitHub (Apr 25, 2020):
Yes, it is important to make this message more clear to the user. I created issue #434 so it can be translated.
it might be fitting for this issue to extend it on an backup option so user can protect their data from unintended alteration, such as users or hard drive failures.
@Rokt33r commented on GitHub (Apr 26, 2020):
@arcturus140
I think rather than discussing here, we should make more issues to discuss separately. This issue is just for people who lose localStorage for some reasons. So could you create more issues for each specific case? It would be really helpful for me because I still have no idea what kind of problems could happen and how should I deal with it.
@Rokt33r commented on GitHub (Aug 24, 2021):
Won't be fixed since we don't support the legacy cloud storage anymore. This won't happen again in the new cloud space feature.