Data Layer
54 components in the data layer layer
Data Layer components manage data persistence, storage operations, and data access patterns throughout the application.
Data access abstraction that wraps all Supabase Auth API calls behind a clean interface, decoupling the service layer from the specific prov...
Provides secure persistence and retrieval of authentication tokens and biometric credentials using Flutter Secure Storage. Serves as the sin...
Local cache layer for role and membership data fetched from Supabase. Stores resolved role state to local storage for offline resilience, al...
Queries Supabase for the authenticated user's roles and organization memberships. Returns structured role and membership records that are co...
Data access layer managing all CRUD operations for activity records and activity logs in Supabase. Implements RLS-policy-compliant queries s...
Local cache and data access layer for organization-specific activity type definitions seeded in Supabase. Fetches and caches activity types ...
Data access layer for events and event participants, providing CRUD operations and query methods backed by Supabase with RLS policies enforc...
Data access layer for the delegation_grants table, providing read and write operations for all proxy and bulk submission audit records. Enab...
Persists user-level speech input preferences locally using shared_preferences. Stores settings such as preferred recognition locale, noise g...
Data access layer for the activity_documents table, managing CRUD operations for document metadata records (filename, MIME type, size, stora...
Data access layer providing read operations for contacts and peer mentors from Supabase with local caching via Riverpod. Handles offline sce...
Data access layer for creating, reading, updating, and deleting contact notes, backed by Supabase with RLS policies restricting note visibil...
Data access layer responsible for reading and updating peer mentor profile data from Supabase, joining the peer_mentors, certifications, and...
Data access layer managing CRUD operations on the peer_mentor_availability table in Supabase. Handles reading and writing availability statu...
Data access layer for all assignment-related entities: assignments, dispatches, and read receipts. Provides CRUD operations and query method...
Data access layer for peer mentor location records stored as municipality or postal code area centroids in the peer_mentor_locations table. ...
Repository layer responsible for all CRUD operations on the `travel_expense_reports` and `expense_items` Supabase tables with RLS policies s...
Data store that reads and caches expense type configurations from Supabase, enabling per-organisation customisation of available expense typ...
Data access layer for the `receipts` table in Supabase. Handles CRUD operations for receipt records, stores the cloud storage path and gener...
Data access layer for the reimbursement_approvals table, providing CRUD operations and a Riverpod stream provider that subscribes to real-ti...
Data access component managing all read and write operations for the nda_agreements table. Stores signed agreement metadata (user ID, timest...
Data access layer for Bufdir report snapshots and reporting periods. Stores immutable generated report snapshots to ensure auditability even...
Data access layer responsible for querying and caching computed statistics for a peer mentor. Calls the Statistics Calculation Service (edge...
Data access layer that executes aggregation queries against the Supabase database and manages a per-scope-key result cache with invalidation...
Data access layer that maintains a denormalized assignment count field per peer mentor, updated by Supabase database triggers on inserts to ...
Data access layer responsible for executing the similarity queries used by the Duplicate Detection Service. Queries the activities table usi...
Data access layer for the notifications and push_notification_configs tables in Supabase. Provides CRUD operations for notification records,...
Data access layer providing CRUD operations for assignments, assignment_dispatches, and assignment_read_receipts tables in Supabase. Abstrac...
Data access layer for assignment lifecycle management. Implements Supabase row-level security to enforce that peer mentors read only their o...
Data access layer that provides CRUD operations for the impact_summaries table in Supabase, supporting both server-side persistence from the...
Data access layer managing the achievement_badges and user_badges tables. Badge definitions are stored as configuration data to allow admini...
Data access layer for all recruitment and referral data stored in the member_recruitments table. Provides typed CRUD operations for referral...
Data access layer backed by Supabase tables for courses and course_enrollments. Implements row-level security so users can only enroll thems...
Data access layer for certificate and certification renewal records in the Supabase database. Provides type-safe CRUD operations with Supaba...
Data access layer persisting mentor-mentee pairings and milestone data to Supabase. Applies row-level security policies ensuring coordinator...
Data access layer that persists and retrieves all workshop-related records to and from Supabase using the workshop_sessions, workshop_partic...
Data access layer for all admin portal persistence operations, querying user accounts, organizational metadata, settings, and audit records ...
Data access layer for all membership-related persistence operations. Wraps Supabase queries against the user_organization_memberships table ...
Data access layer managing the four linked database tables that form the organizational hierarchy: organizations, national_associations, reg...
Data access layer responsible for reading and writing organization label configurations in Supabase. Manages the org_labels table, providing...
Data access layer for all power of attorney and encrypted document records, providing CRUD operations with RLS enforcement. Handles document...
Persists and retrieves per-user accessibility preferences including screen reader mode, sensitive field warning configuration, preferred aud...
Manages persistence and retrieval of per-user accessibility preference records from the Supabase backend, including cognitive mode, font sca...
Data access layer responsible for reading and writing accessibility preference records (font scale, contrast theme) to Supabase. Supports cr...
Manages per-organization integration configuration records including API credentials, field mappings, feature flags, and enabled connector t...
Provides read and write access to the sync_logs table, recording all outbound sync attempts with their status, payload hashes, and error det...
Data access layer for all member synchronization state, including last-sync timestamps, conflict resolution rules, sync logs, and integratio...
Data access layer that persists portal integration configuration, deep link mappings, feature ownership flags, and sync logs. Provides typed...
Data access layer responsible for fetching and caching the coordinator's scoped member list from Supabase. Constructs complex queries joinin...
Data access layer managing all CRUD operations for activity corrections, approval records, and associated audit trails within Supabase. Scop...
A Riverpod provider (or BLoC) that holds and exposes the current active tab index, the authenticated user's role, and any pending deep link ...
Data access layer for user preferences, bridging local shared_preferences storage and the Supabase accessibility_preferences and theme_confi...
The centralized Dart token definition layer implemented as a Flutter ThemeExtension with typed token classes for colors, typography (TextThe...
Defines the complete relational database schema for all application tables managed via Supabase migrations stored in /supabase/migrations un...
Other Component Types
User Interface components handle presentation logic, user interactions, and visual elements of the application.
Service Layer components contain business logic, orchestrate operations, and provide core application functionality.
Infrastructure components provide foundational utilities, system integrations, and supporting functionality for the application.