feature(mobile): add offline support #1506
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR mostly changes mobile:
Asset
is now a DB entity and contains all required fields, no longer stored anAssetResponseDto
internallyAssetResponseDto
withAsset
: To unify viewing local/remote assetsCachedNetworkImage
withImmichImage
: To showAsset
s instead of only remoteAssetResponseDto
sAlbum
: DB entity, can be both device local and remoteAlbumResponseDto
withAlbum
User
: DB entity, equivalent to server entityValue
: DB entity to store different single values (string/json/int) in a DB table, for configuration settings, logged in user id etc.To test this, you need to run
flutter pub run build_runner build
to generate the Isar files (currently not included in the repo, but we could do that)Since this changeset is already huge, any more advances offline functionalities enabled by this change are planned as follow-up PRs such as: