brick_offline_first_with_supabase 0.1.0+1 copy "brick_offline_first_with_supabase: ^0.1.0+1" to clipboard
brick_offline_first_with_supabase: ^0.1.0+1 copied to clipboard

A Brick domain that routes data fetching through local providers before a Supabase provider.

brick_offline_first_with_supabase workflow

OfflineFirstWithSupabaseRepository streamlines the Supabase integration with an OfflineFirstRepository.

The OfflineFirstWithSupabase domain uses all the same configurations and annotations as OfflineFirst.

Repository #

The repository utilizes the OfflineFirstWithRestRepository's queue because the Supabase client is a thin wrapper around the PostgREST API. There's a small amount of configuration to apply this queue:

// import brick.g.dart and brick/db/schema.g.dart

class MyRepository extends OfflineFirstWithSupabaseRepository {
  static late MyRepository? _singleton;

  MyRepository._({
    required super.supabaseProvider,
    required super.sqliteProvider,
    required super.migrations,
    required super.offlineRequestQueue,
    super.memoryCacheProvider,
  });

  factory MyRepository() => _singleton!;

  static void configure({
    required String supabaseUrl,
    required String supabaseAnonKey,
  }) {
    // Convenience method `.clientQueue` makes creating the queue and client easy.
    final (client, queue) = OfflineFirstWithSupabaseRepository.clientQueue(
      // For Flutter, use import 'package:sqflite/sqflite.dart' show databaseFactory;
      // For unit testing (even in Flutter), use import 'package:sqflite_common_ffi/sqflite_ffi.dart' show databaseFactory;
      databaseFactory: databaseFactory,
    );

    final provider = SupabaseProvider(
      SupabaseClient(supabaseUrl, supabaseAnonKey, httpClient: client),
      modelDictionary: supabaseModelDictionary,
    );

    // Finally, initialize the repository as normal.
    _singleton = MyRepository._(
      supabaseProvider: provider,
      sqliteProvider: SqliteProvider(
        'my_repository.sqlite',
        databaseFactory: databaseFactory,
        modelDictionary: sqliteModelDictionary,
      ),
      migrations: migrations,
      offlineRequestQueue: queue,
      memoryCacheProvider: MemoryCacheProvider(),
    );
  }
}
copied to clipboard

When using supabase_flutter, create the client and queue before initializing:

final (client, queue) = OfflineFirstWithSupabaseRepository.clientQueue(databaseFactory: databaseFactory);
await Supabase.initialize(httpClient: client)
final supabaseProvider = SupabaseProvider(Supabase.instance.client, modelDictionary: ...)
copied to clipboard

Models #

ConnectOfflineFirstWithSupabase #

@ConnectOfflineFirstWithSupabase decorates the model that can be serialized by one or more providers. Offline First does not have configuration at the class level and only extends configuration held by its providers:

@ConnectOfflineFirstWithSupabase(
  supabaseConfig: SupabaseSerializable(),
  sqliteConfig: SqliteSerializable(),
)
class MyModel extends OfflineFirstWithSupabaseModel {}
copied to clipboard

FAQ #

Why can't I declare a model argument?

Due to an open analyzer bug, a custom model cannot be passed to the repository as a type argument.

Unsupported Field Types #

  • Any unsupported field types from SupabaseProvider, or SqliteProvider
  • Future iterables of future models (i.e. Future<List<Future<Model>>>).
12
likes
0
points
2.96k
downloads

Publisher

unverified uploader

Weekly Downloads

2024.09.08 - 2025.03.23

A Brick domain that routes data fetching through local providers before a Supabase provider.

Homepage
Repository (GitHub)
View/report issues

License

unknown (license)

Dependencies

brick_core, brick_offline_first, brick_offline_first_with_rest, brick_sqlite, brick_supabase, http, logging, meta, sqflite_common

More

Packages that depend on brick_offline_first_with_supabase