Skip to content

feat: Improve local backup robustness and UX #1015

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Sep 15, 2025
Merged

feat: Improve local backup robustness and UX #1015

merged 3 commits into from
Sep 15, 2025

Conversation

@SameDesu123
Copy link
Contributor

@SameDesu123 SameDesu123 commented Aug 14, 2025 •
edited
Loading

PR Checklist

  • Have you checked if it works normally in all models? Ignore this if it doesn't use models.
  • Have you checked if it works normally in all web, local, and node hosted versions? If it doesn't, have you blocked it in those versions?
  • Have you added type definitions? (assetMap, missingAssets)

Description

  • Fixes a TypeError when local backup encounters null asset data, preventing the process from crashing.
  • Implements real-time and final summary reporting for skipped assets during backup.
477847494-a57201fe-6559-446a-ad31-07240f9184bb
  • Uses user-friendly asset and character names in reports.
  • Consolidates final success/failure alerts into a single summary dialog.
477847503-dfb24efa-41da-4996-af37-5ad7892dcce4

@SameDesu123
feat(backup): Improve local backup robustness and UX
8071d86 
- Fixes a TypeError when local backup encounters null asset data, preventing the process from crashing.
- Implements real-time and final summary reporting for skipped assets during backup.
- Uses user-friendly asset and character names in reports.
- Consolidates final success/failure alerts into a single summary dialog.

Fixes kwaroran#1013
@SameDesu123 SameDesu123 changed the title feat(backup): Improve local backup robustness and UX feat: Improve local backup robustness and UX Aug 14, 2025
@SameDesu123
Copy link
Contributor Author

SameDesu123 commented Aug 14, 2025 •
edited
Loading

477847494-a57201fe-6559-446a-ad31-07240f9184bb The way skipped assets are displayed during the backup process seems messy. What would be a good way to handle this? I wanted to use a markdown format with `alertMd`, but I couldn't because it requires `alertWait` in that state.

@kwaroran kwaroran merged commit 9d7877f into kwaroran:main Sep 15, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@SameDesu123 @kwaroran