mirror of
https://github.com/immich-app/immich
synced 2026-08-29 13:15:45 +00:00
- Introduced new storage status options: "On Device Only", "On Server Only", and "All" in search filters. - Updated search service to handle filtering based on storage status, allowing for device-only or server-only asset searches. - Enhanced UI components to support new storage status filters, including a dedicated picker for selecting storage options. - Adjusted existing search logic to accommodate new filtering criteria and ensure proper asset retrieval based on selected storage status. |
||
|---|---|---|
| .. | ||
| entities | ||
| loaders | ||
| repositories | ||
| utils | ||
| mapper.dart | ||
| README.md | ||
Infrastructure Layer
This directory contains the infrastructure layer of Immich. The infrastructure layer is responsible for the implementation details of the app. It includes data sources, APIs, and other external dependencies.
Structure
- Entities: These are the classes that define the database schema for the domain models.
- Repositories: These are the actual implementation of the domain interfaces. A single interface might have multiple implementations.
- Utils: These are utility classes and functions specific to infrastructure implementations.
infrastructure/
├── entities/
│ └── user.entity.dart
├── repositories/
│ └── user.repository.dart
└── utils/
└── database_utils.dart
Usage
The infrastructure layer provides concrete implementations of repository interfaces defined in the domain layer. These implementations are exposed through Riverpod providers in the root providers directory.
// In domain/services/user.service.dart
final userRepository = ref.watch(userRepositoryProvider);
final user = await userRepository.getUser(userId);
The domain layer should never directly instantiate repository implementations, but instead receive them through dependency injection.