You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Successful migrations showed warnings for expected exclusions, while
View Report only refreshed an already displayed summary. Development
startup also required a manually built Migrator and an environment flag.
- Open report details with per-domain results and grouped explanations.
- Treat excluded session paths and orphaned parent relationships as
informational, and count warnings by their actual severity.
- Exclude normal built-in MiniApp storage imports from conflict counts
while preserving existing target-conflict handling.
- Simplify migration instructions in English and both Chinese locales.
- Automatically retry denied Windows Job breakaway in Debug builds
without an environment flag; retain Release launch behavior.
- Incrementally build Data Migrator before Desktop dev and preview
startup, and stop with an error if preparation fails.
Validation: focused migration tests, Web and locale checks, Migrator
script checks, and dev script syntax checks passed. Application startup
and UI interaction were not exercised.
Copy file name to clipboardExpand all lines: OpenBitFun-Installer/src/i18n/locales/en.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -226,7 +226,7 @@
226
226
},
227
227
"complete": {
228
228
"finish": "Finish",
229
-
"migrateLegacyData": "Migrate old BitFun data after installation",
229
+
"migrateLegacyData": "Migrate legacy data after installation",
230
230
"migrateLegacyDataDescription": "Starts the installed Data Migrator. It keeps the old data unchanged, asks you to confirm the scope, and reopens OpenBitFun when migration ends."
"summaryEn": "Scan and import supported data from a local legacy BitFun installation, inspect redacted reports, and leave the legacy source unchanged.",
"reasonEn": "Scanning depends on legacy data on the current device, live scope selection, and result state; the Agent opens the exact entry and keeps selection and scanning visible to the user.",
0 commit comments