Using SingleProviderRepository with Supabase does not generate adapters

[Fabricio-191]

Hello, i am currently using brick with Supabase, but i am not yet using the offline first arquitecture (that's for the future me)

For this as the docs says i am using the SingleProviderRepository like this:

class Repository<TModel extends SupabaseModel> extends SingleProviderRepository<TModel> {
  Repository._privateConstructor(super.supabaseProvider);

	SupabaseClient get supabaseClient => Supabase.instance.client;

  static Future<void> init() async {
    await Supabase.initialize(
      url: 'my url obviously',
      anonKey: 'the key to other project obviously',
      postgrestOptions: const PostgrestClientOptions(schema: 'api'),
      storageOptions: const StorageClientOptions(retryAttempts: 1),
    );

    repository = Repository._privateConstructor(
      SupabaseProvider(
        Supabase.instance.client,
        modelDictionary: supabaseModelDictionary,
      ),
    );

    await repository.initialize();
  }
}

And i have two problems, first, when running dart run build_runner build it does not generates adapters for my models and in brick.g.dart the supabaseMappings is empty

I annotated all my models like this:

import 'package:brick_supabase/brick_supabase.dart';

@SupabaseSerializable(tableName: 'activities_ratings')
class ActivityRating extends SupabaseModel {
  ActivityRating({
    required this.userId,
    required this.activityId,
    required this.comment,
    required this.rating,
    required this.createdAt,
    required this.updatedAt,
  });

  final String userId;
  final String activityId;
  final String? comment;
  final int rating;
  //
  final DateTime createdAt;
  final DateTime updatedAt;
}

// this is in a file named:  activity_rating.model.dart

I followed this example, with the difference of the SupabaseSerializable annotation

My second problem is that i am missing a subscribe or subscribeToRealtime method, because SingleProviderRepository only implements delete, get, upsert methods

This is not an error as SingleProviderRepository is generic and subscribeToRealtime is something specific to Supabase, but i would be nice having a SupabaseRepository with a subscribe method

[tshedor]

@Fabricio-191 These are separate issues; in the future, could you please open them separately? It helps others find their own answers. I'll answer both here for now.

For this as the docs says i am using the SingleProviderRepository like this:

Thank you for raising this. I will remove these docs, they're confusing and unnecessary. I would instead recommend instantiating and accessing the provider directly if you're only using one provider; i.e. you just call SupabaseProvider.

And i have two problems, first, when running dart run build_runner build it does not generates adapters for my models and in brick.g.dart the supabaseMappings is empty

This is another rare case that I should be more clear about. There isn't a "need" to generate a mapping for adapters since you're only using one provider and you aren't using a repository.

To solve this, use the offline first generator and .gitignore anything in db/. While you'll have generated serdes for SQLite in your adapters, you can just ignore them.

On a more technical level, while each of these providers has a generator, only the offline first packages have builders. The generators simply produce the strings that the builders save. The problem you're likely experiencing is you don't have an explicit build.yaml that combines these generators within a build file.

I will add documentation around this, thank you for bringing it to light.

My second problem is that i am missing a subscribe or subscribeToRealtime method, because SingleProviderRepository only implements delete, get, upsert methods

You're right, this method should mostly exist in the SupabaseProvider. I'm going to port some of the functionality, but the reactive parts of subscribeToRealtime will stay in the repository, since the repository is stateful in subscription management and has implicit idea of how to handle events from Supabase.

[Fabricio-191]

I would instead recommend instantiating and accessing the provider directly if you're only using one provider; i.e. you just call SupabaseProvider.

There isn't a "need" to generate a mapping for adapters since you're only using one provider and you aren't using a repository.

The problem with using the SupabaseProvider is that it stills needs the adapters for the models to be generated (link), which was what i wanted, to have a type safe way of reading the data instead of reading it from JSON

To solve this, use the offline first generator

I get this error

Unhandled Exception: type 'Repository' is not a subtype of type 'OfflineFirstWithSupabaseRepository<OfflineFirstWithSupabaseModel>?' of 'repository'

Because adapters expect a OfflineFirstWithSupabaseRepository

[tshedor]

@Fabricio-191 ok, so just the repository then.

For SQLite, you could use the in-memory database factory. This is recreated on app start, so nothing persists and your local data is effectively ephemeral. If you make all of your .upsert requests .awaitRemote you won't hit the queue either.

[tshedor]

@Fabricio-191 did the repository method work?

[Fabricio-191]

I didn't try, i just overrided the get/subscribe methods to change the default OfflineFirstGetPolicy to OfflineFirstGetPolicy.awaitRemote

[tshedor]

@Fabricio-191 sounds like you found a solution; closing this issue