A week that starts where the person reading it starts theirs

The scheduler's day picker began on Sunday because that is where Intl numbers the days from, which is a fact about the API and not about anybody's week. Monday leads it across most of Europe. A row of seven buttons in the wrong order is not just odd to read — it is easy to misclick, and a misclicked day in a schedule is a car charging on the wrong night. So Settings › Appearance asks, beneath the date and the clock, as the third question a region gets: first day of the week, following the region unless it is answered outright. The same shape the time format already had, and the same "auto" default, so nothing changes for an account that never opens it. The rule lives in lib/format.js beside the clock's, with the ordering, the day names and the sort all coming from there. The two places that lay weekdays out — the picker and the line each task is summarised on — read it rather than each keeping an opinion, so a day set is written and read back in the same order. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-03 23:12:10 +02:00
parent 5a4515978f
commit 0f48093d1a
12 changed files with 154 additions and 32 deletions
@@ -262,6 +262,10 @@ var collectionsSchema = map[string][]fieldDef{
 		// "auto" is the region's own convention, which is what every clock in the
 		// app read before this field existed.
 		fSelect("time_format", []string{"auto", "24", "12"}, false),
+		// The day a week is drawn as starting on, wherever weekdays are laid out
+		// in a row. "auto" is the region's own convention, which is what the
+		// scheduler's day picker read before this field existed.
+		fSelect("week_start", []string{"auto", "monday", "sunday"}, false),
 		fSelect("currency", []string{
 			"EUR", "GBP", "CHF", "PLN", "CZK", "HUF", "RON", "BGN", "DKK", "SEK", "NOK",
 			"ISK", "ALL", "AMD", "AZN", "BAM", "BYN", "GEL", "MDL", "MKD", "RSD", "RUB",