Skip to content

2026.08.17 - Statusbar Sidebar Visibility - Phase 1: Backward-Compatible Config Schema - #85

Merged
lanhhoang merged 6 commits into
masterfrom
20260817-statusbar-sidebar-visibility-phase-1-config
Aug 18, 2026
Merged

lanhhoang merged 6 commits into
masterfrom
20260817-statusbar-sidebar-visibility-phase-1-config

Conversation

@lanhhoang

Copy link
Copy Markdown
Contributor
  • Implement statusbar and sidebar visibility configuration

Phase 1 of the statusbar/sidebar visibility plan. Both fields are required
booleans on PiStatusConfig with enabled-by-default semantics; only the
literal stored value false disables a field, all other values (missing,
true, null, 0, strings, objects, arrays) normalize to true. saveConfig
emits both fields in the canonical serialized schema.
Phase 1 of the statusbar/sidebar visibility plan. Adds a new
`config — surface visibility` describe block asserting:
- both fields default to true when absent
- non-false values (true, null, 0, 'false', {}, []) normalize to true
- literal false disables only the targeted surface
- saveConfig round-trips both fields and includes them in the
  serialized schema

Also adds the new fields to the canonical in-memory fixture and updates
exact-equality expectations in malformed/missing-config and serialized-
key tests to match the new schema.
Phase 1 of the statusbar/sidebar visibility plan. Both fields are now
required on PiStatusConfig, so every in-memory typed fixture across
the test suite needs the defaults (true, true). Also updates one
persisted-schema expectation in index.test.ts to include the new keys
in the round-tripped JSON.
@lanhhoang
lanhhoang merged commit e52de76 into master Aug 18, 2026
1 check passed
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