order media so that latest added are top #660
无评审员
标签
未选择标签
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
未选择里程碑
暂无项目
未指派成员
2 位参与者
通知
到期时间
未设置到期时间。
依赖工单
没有设置依赖项。
引用:Plume/Plume#660
正在加载…
添加表格
在新工单中引用
没有提供说明。
删除分支 "feature/621"
删除分支是永久的。虽然已删除的分支在实际被删除前有可能会短时间存在,但这在大多数情况下无法撤销。是否继续?
partial fix for #621
Codecov Report
❓
@ -66,0 +67,4 @@
medias::table
.filter(medias::owner_id.eq(owner))
.order(medias::id.desc())
.load::<Self>(conn)
is this guaranteed to be such?
do we have a create date anywhere?
@ -66,0 +67,4 @@
medias::table
.filter(medias::owner_id.eq(owner))
.order(medias::id.desc())
.load::<Self>(conn)
we don't have date, and the ids we use are monotonic counter, unless we overflow that 64b signed counter (not likely to happen)
@ -66,0 +67,4 @@
medias::table
.filter(medias::owner_id.eq(owner))
.order(medias::id.desc())
.load::<Self>(conn)
i wonder if anyone expects that editing a media pushes it to the top again…
@ -66,0 +67,4 @@
medias::table
.filter(medias::owner_id.eq(owner))
.order(medias::id.desc())
.load::<Self>(conn)
We can't edit media information for the moment, so…
@ -66,0 +67,4 @@
medias::table
.filter(medias::owner_id.eq(owner))
.order(medias::id.desc())
.load::<Self>(conn)
well then… pushes [resolve] button
Ideally, it should be done for the paginated version too, so that
/media
lists them in the correct order.👍