Fix conversationId comparison bug using integer format (!781) · Merge requests · Pleroma / pleroma-fe

Tae Hoon requested to merge tae/pleroma-fe:519 into develop May 03, 2019

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.

Fix conversationId comparison bug using integer format