mirror of
https://github.com/immich-app/immich.git
synced 2025-06-23 15:30:51 -04:00
bcda2c6e22
* wip: timeline * more segment extensions * added scrubber * refactor: timeline state * more refactors * fix scrubber segments * added remote thumb & thumbhash provider * feat: merged view * scrub / merged asset fixes * rename stuff & add tile indicators * fix local album timeline query * ignore hidden assets during sync * ignore recovered assets during sync * old scrubber * add video indicator * handle groupBy * handle partner inTimeline * show duration * reduce widget nesting in thumb tile * merge main * chore: extend cacheExtent * ignore touch events on scrub label when not visible * scrub label ignore events and hide immediately * auto reload on sync * refactor image providers * throttle db updates --------- Co-authored-by: shenlong-tanwen <139912620+shalong-tanwen@users.noreply.github.com> Co-authored-by: Alex Tran <alex.tran1502@gmail.com>
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.