immich/mobile/lib/domain
Brandon Wees b484a52252
chore: refactor show view in timeline button (#22894)
* chore: refactor show view in timeline button

This refactor includes changes to notify asset viewer about where an asset was shown from.

* chore: realized I could just pull from the timelineProvider instead of storing it in the asset viewer state

* chore: rename enum to TimelineOrigin and update members

* fix: update isOwner condition

---------

Co-authored-by: Alex <alex.tran1502@gmail.com>
2025-10-14 15:25:48 +00:00
..
interfaces refactor(mobile): interfaces refactor (#19415) 2025-06-23 11:27:44 -05:00
models fix: show dialog before delete local action (#22280) 2025-10-14 07:20:14 +00:00
services chore: refactor show view in timeline button (#22894) 2025-10-14 15:25:48 +00:00
utils fix: improve sync backup error indicator (#22527) 2025-10-03 13:36:44 +00:00
README.md refactor(mobile): split store into repo and service (#16199) 2025-02-19 13:05:24 -06:00

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.