immich/mobile/lib/infrastructure
Adam Gastineau 27a29b6fab
chore(mobile): remove Drift generated code (#30297)
* chore(mobile): remove Drift generated code

* Remove Drift test generated files from tree

* Make static_analysis use the shared mobile:codegen action

* Remove static_analysis generated file diffing
2026-07-29 20:29:07 +00:00
..
entities chore(mobile): remove Drift generated code (#30297) 2026-07-29 20:29:07 +00:00
loaders fix(mobile): fix 10-bit heic and avif colors on android (#29631) 2026-07-06 21:16:09 +00:00
repositories chore(mobile): remove Drift generated code (#30297) 2026-07-29 20:29:07 +00:00
utils feat(mobile): add three-state field serialization (#27231) 2026-06-03 08:13:17 -04:00
mapper.dart refactor: partner-page (#28783) 2026-06-04 09:05:45 -04:00
README.md refactor(mobile): split store into repo and service (#16199) 2025-02-19 13:05:24 -06:00

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.