Skip to content

Don't save default settings over ones that failed to load - #636

Merged
clstaudt merged 1 commit into
mainfrom
settings-load-errors
Oct 19, 2026
Merged

clstaudt merged 1 commit into
mainfrom
settings-load-errors

Conversation

@clstaudt

Copy link
Copy Markdown
Contributor

When the invoicing preferences or the currency settings failed to load, Settings showed the built-in defaults as if they were the user's own: EUR, a 1% fee, daily numbering, English, EN16931. Save then wrote them over the real settings. A profile that failed to load came back empty, ready to be saved over the real one.

  • A failed load shows an error with Retry in place of the form. Save stays off until the settings have loaded.
  • The core reports a profile or currency setting it can't read as an error, instead of an empty profile or a guessed country.

馃 Generated with Claude Code

When the invoicing preferences or the currency settings failed to load,
Settings showed the built-in defaults as if they were the user's own:
EUR and a 1% conversion fee, the daily number scheme, English, the
default template and EN16931. Pressing Save then wrote those defaults
over the real settings. A profile that failed to load came back as an
empty profile, which Save would write over the real one as well.

A failed load now shows an error with Retry in place of the form, and
Save stays off until the settings have loaded. The core reports a
profile it cannot read as an error instead of an empty one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@clstaudt
clstaudt added this pull request to the merge queue Oct 19, 2026
Merged via the queue into main with commit f526d67 Oct 19, 2026
3 checks passed
@clstaudt
clstaudt deleted the settings-load-errors branch October 19, 2026 06:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant