From bd42c86796ae22f3053994ce8a9348e0c954583e Mon Sep 17 00:00:00 2001 From: Administrator Date: Sat, 23 May 2026 15:46:27 +0200 Subject: [PATCH] ux(log): clarify logToFile also affects restart dedup MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Deep bug-hunt of the per-hoster logToFile feature found the feature itself clean (7 data flows traced: secret-store leaves hosterSettings alone, save round-trip preserves the key for account-less hosters, backup import/export round-trips, updateSettings full-replaces with default-true fallback, checkbox branch precedes numeric coercion, boolean survives IPC→JSON→parse intact). The one real interaction effect: _autoDeduplicateFromLog reads fileuploader.log on startup to drop already-uploaded files from the restored queue. With logToFile off for a hoster, its entries are absent, so the same file could be re-uploaded after a restart. The dedup↔log coupling predates this feature; the toggle just makes it observable. Make it transparent in the checkbox hint rather than silently shipping the surprise. Full decoupling (a separate always-written dedup index independent of the user-facing log) is a larger, separate change with its own risk surface — deferred unless wanted. 147/147 tests still green. --- renderer/app.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/renderer/app.js b/renderer/app.js index b462fdd..2c7b9a2 100644 --- a/renderer/app.js +++ b/renderer/app.js @@ -2829,7 +2829,7 @@ function renderSettings() {
- Erfolgreiche Links dieses Hosters in fileuploader.log + Erfolgreiche Links in fileuploader.log. Aus = auch kein Doppel-Upload-Schutz beim Neustart für diesen Hoster.