fix(web): stack updates require unstack-restack #20348
Open
+64
−78
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
- optionally adds a primary asset - updates the asset and its stack - removes the non-primary assets
jrasm91
reviewed
Jul 30, 2025
jrasm91
approved these changes
Jul 31, 2025
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
Adds a new action to refresh a stack (change primary asset, remove asset from). Optionally will add a primary asset to the timeline manager (needed for change-primary-asset). Then updates the stack asset and makes sure all non-primary assets are removed from timeline.
Suggested by jrasm in #19703
How Has This Been Tested?
Create stack then change primary asset or remove assets and verify the stack and counts are correct, and any unstacked assets are now in the timeline
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/)