brick_supabase 2.1.1
brick_supabase: ^2.1.1 copied to clipboard
Supabase connector for Brick, a data persistence library. Includes annotations, adapter, model, and provider.
2.1.1 #
- Fix test timeouts caused by
SupabaseMockServer
2.1.0 #
- Add
SupabaseProvider#subscribeToRealtimeto subscribe to Supabase channels. - Add
SupabaseProvider#queryToPostgresChangeFilterto convertQuerys for Supabase subscriptions
2.0.0 #
1.4.1+1 #
- Add
SupabaseProviderQuery - Support defining
upsertMethodviaSupabaseProviderQuery - Fix
orderByqueries to use the column name instead of the field name when constructing PostgREST queries
1.4.0 #
- DEPRECATION remove
Supabase#nullable. Builders should evaluate the nullable suffix of the field instead
1.3.0 #
- When testing realtime responses,
realtime: truemust be defined inSupabaseRequest. This also resolves a duplicateemitsbug in tests; the most common resolution is to remove the first duplicated expected response (e.g.emitsInOrder([[], [], [resp]])becomesemitsInOrder([[], [resp]])) - Associations are not serialized in the
SupabaseResponse; only subscribed table data is provided
1.2.0 #
- DEPRECATION
Query(providerArgs: {'limitReferencedTable':})has been removed in favor ofQuery(limitBy:)#510 - DEPRECATION
Query(providerArgs: {'orderByReferencedTable':})has been removed in favor ofQuery(orderBy:)#510 - Association, plural ordering is supported. For example,
Query(orderBy: [OrderBy.desc('assoc', associationField: 'name')])onDemoModelwould produce the PostgREST filter:orderBy('name', referencedTable: 'association_table') - New
SupabaseProviderQueryadds Supabase-specific support for the newQuery. - Advanced, plural limiting is supported. For example,
Query(limitBy: [LimitBy(1, evaluatedField: 'assoc'))is the equivalent of.limit(1, referencedTable: 'demo_model').Query#limitcan be used in conjunction on the parent model request. - Upgrade
brick_coreto1.3.0 - Update analysis to modern lints
- Add
SupabaseProvider#updateandSupabaseProvider#insertto conform to Supabase policy restrictions - Use
columnNameinstead ofevaluatedFieldinQuerySupabaseTransformerwhen searching for non null associations
1.1.3 #
- Add
query:to@Supabaseto override the generated query at runtime - Support
@Supabase(query:)inQuerySupabaseTransformerandRuntimeSupabaseColumnDefinition
1.1.2 #
- Add
'offset'to Supabase's handledQuery(providerArgs:)
1.1.1 #
- Fix a query builder infinite recursion bug where a parent has a child that has a parent association
- Use declared Supabase
columnNamewhen requesting an association from Supabase - Do not declare a
:tableNameon a Supabase query if no table name is available on the adapter. This should never happen since the code is generated
1.1.0 #
- Reorganized
testing.darttosrc/testing - Added support for stream mocking to
SupabaseMockServer
1.0.5 #
- Add
onConflicttoSupabaseProvider#upsertrequests (#467) @sonbs21
1.0.4 #
- Expose private methods
SupabaseProvider#upsertByTypeandSupabaseProvider#recursiveAssociationUpsertas protected methods
1.0.3 #
- Remove
selectfrom#delete
1.0.2 #
- Only specify key lookup in query transformer if
RuntimeSupabaseColumnDefinition#foreignKeyis specified
1.0.1 #
- Add
@Supabase(foreignKey:)to specify association querying - Add
RuntimeSupabaseColumnDefinition#foreignKeyto track@Supabase(foreignKey:)values
1.0.0 #
- Stable release
0.1.1 #
- Resolve
QuerySupabaseTransformerbugs - Fix table name collision in offline adapter (#416)
0.1.0 #
- Alpha release
0.0.1 #
- Initial