-
Notifications
You must be signed in to change notification settings - Fork 75
feat: improve splitview horizontal image pairing #568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Zaida-3dO
wants to merge
4
commits into
immichFrame:main
Choose a base branch
from
Zaida-3dO:feature/splitview-pairing
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+62
−26
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
a2ff2e5
Improve splitview pairing and pass clientIdentifier on asset requests
Zaida-3dO 5c9b6ae
fix: rename isHorizontal to isPortrait for clarity
Zaida-3dO 30f5330
chore: add clarifying comments to selectAssetsForDisplay
Zaida-3dO 3ece987
fix: correct image order when navigating backwards
Zaida-3dO File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Portrait image at index 0 can get stuck indefinitely in the backlog.
When the first candidate is portrait and no other portrait exists to pair with (lines 250-252), returning
[1]removes only the landscape at index 1. The portrait at index 0 remains in the backlog. On subsequent iterations, if the backlog continues to have only landscapes after this portrait, the same portrait will repeatedly stay stuck while landscapes are consumed.Consider falling back to displaying the lone portrait instead of skipping it:
🐛 Proposed fix
Alternatively, if the intent is to prioritize landscapes over lone portraits, consider a different backlog management strategy that doesn't leave portraits stuck.
🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is acceptable, if you have splitview set to true.
Maybe i just update the docs to explain this caveat, will wait for human input before I make any change here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Zaida-3dO, understood! That's a reasonable approach—documenting the behavior keeps users informed about how splitview handles mixed portrait/landscape content. If you'd like any help drafting the documentation for this caveat, feel free to ask. Otherwise, I'll defer to the human feedback you're waiting for. 👍