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
fix: memory lane assets in ascending order #8309
Conversation
Deploying immich with Cloudflare Pages
|
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.
Nice!
@@ -131,7 +131,9 @@ export function mapAsset(entity: AssetEntity, options: AssetMapOptions = {}): As | |||
} | |||
|
|||
export class MemoryLaneResponseDto { | |||
@ApiProperty({ deprecated: true }) | |||
title!: string; |
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.
My initial thought for this property is that we will have more categories, not just x year ago
, but perhaps the best shots of the month
...etc.
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.
It doesn't work very well with translations though. I think sending back text in an API always gets complicated when dealing with i18n. We can probably add a type field if we start supporting another category of memories.
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.
Basically metadata and types are probably the easy to go and the clients can translate it into titles
response.title
(client can do this using translations andyearsAgo
)