mirror of https://github.com/kuhyx/utils.git synced 2026-11-10 21:27:14 +01:00

History

Krzysztof kuhy Rudnicki 704c67ebbd Raise the very_good_analysis floor to 10.3.0 in the four Flutter libs A caret range's floor is the only comparable number it carries, and all four libs sat at ^10.2.0 while 10.3.0 was current. The Q13 carve-out lets these lint packages keep a caret; it does not let the floor rot. Deliberately its own commit, separate from any dependency bump: a lint-package major/minor lands new rules across four packages at once, and tangling that with a resolution change would make an analyze cascade indistinguishable from a version conflict. `flutter analyze` is clean in all four, and all four suites pass unchanged (88 / 68 / 24 / 35). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK		2026-08-28 13:07:41 +02:00
..
lib	Fix two long-red CI gates: palette_check path after md rename, file-length in sync_settings_ui	2026-08-28 12:36:41 +02:00
scripts	crdt_sync_dart: latest stable + exact pins, 100% coverage, CI for both crdt_sync packages	2026-08-28 12:32:24 +02:00
test	Fix two long-red CI gates: palette_check path after md rename, file-length in sync_settings_ui	2026-08-28 12:36:41 +02:00
.gitignore	Add sync_settings_ui: shared Firebase-only sync settings screen	2026-08-12 23:10:17 +02:00
.pre-commit-config.yaml	Fix the cap hook in CI, and the re-exports its --all-files run exposed	2026-08-22 15:52:59 +02:00
analysis_options.yaml	sync_settings_ui: split sync_settings_screen.dart 382 -> 192	2026-08-22 15:38:58 +02:00
pubspec.yaml	Raise the very_good_analysis floor to 10.3.0 in the four Flutter libs	2026-08-28 13:07:41 +02:00
README.md	Extract the Flutter sync glue into crdt_sync_flutter, and document it	2026-08-22 17:26:34 +02:00

README.md

sync_settings_ui

The shared Sync settings screen: Firebase sign-in (email/password or Google one-tap), Disconnect, a live status line, and an optional Backup section. Reused across every one of kuhy's Flutter apps that syncs, so the screen behaves identically everywhere and is fixed in one place.

Generalized from the near-identical _connectFirebase / _connectGoogle / _disconnectFirebase / _load logic that had been duplicated into every app's settings screen.

Install

dependencies:
  sync_settings_ui:
    git:
      url: https://github.com/kuhyx/utils
      ref: sync_settings_ui-v0.1.0
      path: sync_settings_ui

Usage

This package never touches flutter_secure_storage or google_sign_in itself — every keystore read/write and every platform sign-in arrives as an already-built closure. crdt_sync_flutter provides all of them, so the two fit together directly:

import 'package:crdt_sync_flutter/crdt_sync_flutter.dart';
import 'package:sync_settings_ui/sync_settings_ui.dart';

SyncSettingsScreen(
  accountLoader: () => loadAccount(),
  accountSaver: saveAccount,
  accountClearer: clearAccount,
  sessionProbe: () => isSyncConfigured(kApp),
  firebaseFactory: () => openSync(kApp),
  googleFirebaseFactory: () => signInWithGoogle(
    kApp,
    tokenFetcher: googleIdToken, // the app's own google_sign_in call
  ),
  googleAvailable: googleSignInSupported,
  backup: BackupSlot(label: 'notes', export: _export, import: _import),
)

Pass backup: null to omit the Backup section entirely.

What it gets right, so you don't re-derive it

"Connected" means the session probe says so — never that a factory returned a non-null client. FirebaseSyncController returns a FirebaseConnectResult carrying a six-case outcome:

Outcome	Meaning
`connected`	Signed in, and the probe confirms a live session.
`rejected`	The credentials were refused.
`cancelled`	The user dismissed the picker.
`signedInButNotPersisted`	Sign-in worked; nothing durable was stored.
`wrongAccount`	Authenticated as a uid the rules do not allow.
`failed`	Anything else.

signedInButNotPersisted and wrongAccount exist because both looked identical to success from the call site and both produced a device that appeared connected and synced nothing.

The Google button is double-gated on supportsGoogle && googleAvailable, so a button that cannot possibly succeed is never rendered — a visible control that always reports "cancelled" is worse than no control.

Development

flutter pub get
flutter analyze
flutter test