Skip to content

Fix conversationId comparison bug using integer format

Tae Hoonrequested to merge
tae/pleroma-fe:519 into develop

closes #519 (closed)

conversationId is integer string while statusId is a unique alphanumeric string with a fixed length.

Comparison of conversationId is quite buggy.

For example: "10" < "2" (this is valid)

To support proper sorting and pagination, I've converted conversationId to an integer.

Merge request reports