From 882d07db5f21b007f6c1ece4516c62c97536dfe7 Mon Sep 17 00:00:00 2001 From: kim Date: Mon, 15 Sep 2025 18:28:48 +0200 Subject: [bugfix] API status edit history returned in inverse order (#4432) Simply reverses the order in which we build status edit history for the frontend. In fact now it matches how we store it in the database which is even easier :p. Why I thought it needed to be returned inverse to begin with? Who knows. closes https://codeberg.org/superseriousbusiness/gotosocial/issues/4426 (thank you [@DarkCat09](https://codeberg.org/DarkCat09) for pointing it out!) Co-authored-by: tobi Reviewed-on: https://codeberg.org/superseriousbusiness/gotosocial/pulls/4432 Co-authored-by: kim Co-committed-by: kim --- internal/db/bundb/statusedit.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'internal/db') diff --git a/internal/db/bundb/statusedit.go b/internal/db/bundb/statusedit.go index ed62c64f1..a896284d8 100644 --- a/internal/db/bundb/statusedit.go +++ b/internal/db/bundb/statusedit.go @@ -96,8 +96,8 @@ func (s *statusEditDB) GetStatusEditsByIDs(ctx context.Context, ids []string) ([ return nil, err } - // Reorder the edits by their - // IDs to ensure in correct order. + // Reorder the edits by their IDs to ensure in correct + // order (ID ascending, ie., latest to oldest edit). getID := func(e *gtsmodel.StatusEdit) string { return e.ID } xslices.OrderBy(edits, ids, getID) -- cgit v1.2.3