mirror of
https://github.com/kuhyx/screen-locker.git
synced 2026-11-11 22:13:54 +01:00
Krzysztof kuhy Rudnicki
d418994f6f
storage_service.dart the class: open, settings, active session
storage_service_schema.dart create / migrate / seed
storage_service_exercises.dart read+write a single exercise's row
storage_service_sessions.dart apply progression, record sessions
storage_service_backup.dart backup, restore, sync markers
Dart cannot continue a class body across files, so unlike history_screen these
are `extension`s in `part` files. Library privacy still applies inside a part,
so they reach `_db` and `_getSetting` unchanged and every caller still writes
`StorageService.instance.foo()` -- no public API change, nothing for
public_member_api_docs to demand.
Doing this exposed a bug in scripts/check_silent_failures_dart.py: its bare
`on Foo {` pattern (the catch clause form) also matched
`extension StorageServiceBackup on StorageService {`, so it reported the
declarations as swallowed exceptions. It now requires the try block's closing
`}` first. Verified both directions on a fixture: a real silent
`} on FormatException {` is still reported, the extension is not.
402 Dart tests still pass; flutter coverage still 100%; dart analyze clean.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EveB813BQ8abAP68VSqZ5Y
|
||
|---|---|---|
| .. | ||
| backup_service.dart | ||
| firebase_backend.dart | ||
| github_device_auth.dart | ||
| google_platform_io.dart | ||
| google_platform_web.dart | ||
| google_platform.dart | ||
| google_sign_in_backend.dart | ||
| http_server_service.dart | ||
| progression_sync_service.dart | ||
| storage_service_backup.dart | ||
| storage_service_exercises.dart | ||
| storage_service_schema.dart | ||
| storage_service_sessions.dart | ||
| storage_service.dart | ||
| sync_device_id.dart | ||
| sync_service.dart | ||
| sync_settings.dart | ||
| sync_state_factory.dart | ||
| sync_status.dart | ||
| workout_sync_service.dart | ||