decentraland / marketplace-server / 31031412856

62%

main: 62%

Pull #385

github

fix: sort the shop item feed by listing date, not item creation

The Shop's default "Newest" sort on /v3/catalog/unified?groupBy=item did not
order by when things were listed, in two distinct ways.

CollectionStore mints carried `to_timestamp(item.created_at)` — when the item
was PUBLISHED on-chain, not when it went on sale. A collection published long
ago and put up for minting today sorted as old. These rows are a large share of
the Shop's default grid (primary-only), so much of it was ordered by item
creation. They now carry `first_listed_at`, the same column the marketplace's
own NEWEST sort reads, coalescing to `created_at` because the squid leaves it
null on an item it never saw listed.

The item-unified grid then ordered on the representative row's own created_at.
That survivor is chosen by DISTINCT ON on price and listing kind, never by
recency, so an item whose fresh resale had just landed still sorted by the date
of the old primary listing that won the grouping. The grouping layer now
exposes item_listed_at — MAX(created_at) over the item's rows — and getShopItems
and getRelatedItems order on that. The window shares listing_count's partition,
so it folds into the same WindowAgg; the previous ORDER BY already sorted the
grouped set rather than riding idx_mv_trades_created_at, so there is no plan
regression.

The API's `createdAt` is deliberately unchanged: it stays the representative
listing's own date, which is what the per-listing feed reports for the same row.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

1657 of 3104 branches covered (53.38%)

Branch coverage included in aggregate %.

3018 of 4477 relevant lines covered (67.41%)

26.14 hits per line