mirror of
https://github.com/immich-app/immich.git
synced 2026-03-05 00:13:44 -05:00
* feat: add playbackStyle to local asset entity and related database schema * implement conversion function for playbackStyle in local sync service * implement conversion function for playbackStyle in local sync service * refactor: remove deducedPlaybackStyle from TrashedLocalAssetEntityData * add playbackStyle column to trashed local asset entity * make playbackStyle non-nullable across the mobile codebase * Streamline playbackStyle backfill: - only backfill local assets playbackStyle in flutter/dart code - only update trashed local assets in db migration * bump target database version to 23 and update migration logic for playbackStyle * set playback_style to 0 in merged_asset.drift as its a getter in base asset * run make pigeon * Populate playbackStyle for trashed assets during native migration
Domain Layer
This directory contains the domain layer of Immich. The domain layer is responsible for the business logic of the app. It includes interfaces for repositories, models, services and utilities. This layer should never depend on anything from the presentation layer or from the infrastructure layer.
Structure
- Interfaces: These are the interfaces that define the contract for data operations.
- Models: These are the core data classes that represent the business models.
- Services: These are the classes that contain the business logic and interact with the repositories.
- Utils: These are utility classes and functions that provide common functionalities used across the domain layer.
domain/
├── interfaces/
│ └── user.interface.dart
├── models/
│ └── user.model.dart
├── services/
│ └── user.service.dart
└── utils/
└── date_utils.dart
Usage
The domain layer provides services that implement the business logic by consuming repositories through dependency injection. Services are exposed through Riverpod providers in the root providers directory.
// In presentation layer
final userService = ref.watch(userServiceProvider);
final user = await userService.getUser(userId);
The presentation layer should never directly use repositories, but instead interact with the domain layer through services.