feat(web): Add asset selection logic to the tagged asset view page #19161
+73
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h that tagged media can be deleted, added to albums, etc
alextran1502
added
changelog:feature
changelog:enhancement
and removed
changelog:feature
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The current asset view when browsing tags allows the user to select media, but does not expose any of the buttons to interact with the media.
This PR copies over the asset selection controller logic from other parts of the codebase (albums), such that media can be deleted, added to albums, etc straight from the tags view - see screenshots provided
How Has This Been Tested?
Ran the UI and tested the buttons manually; see screenshots.
Screenshots
Checklist:
src/services/uses repositories implementations for database calls, filesystem operations, etc.src/repositories/is pretty basic/simple and does not have any immich specific logic (that belongs insrc/services/)