Search results display order does not match API response order

[jteulade]

I have a custom STAC API implementation. When I POST to /search with a sort order, for example:

{
  "limit": 12,
  "collections": [
    "SAOCOM"
  ],
  "sortby": [
    {
      "field": "properties.datetime",
      "direction": "desc"
    }
  ]
}

I get the following response (abridged for clarity):

{
  "type": "FeatureCollection",
  "features": [
    { "id": "20191204T101938_SAOCOM_VV_HH_VH_HV_TN_L1A", ... },
    { "id": "20190131T215100_SAOCOM_VV_SM_L1C", ... },
    { "id": "20181223T103110_SAOCOM_VV_HH_VH_HV_SM_L1D", ... }
  ],
  "links": [
    { "rel": "self", "href": "/search", "type": "application/geo+json" },
    { "rel": "root", "href": "/", "type": "application/json" }
  ],
  "numberReturned": 3
}

The order of the features array is correct in the API response (descending by datetime).
However, in the stac-browser search page, the items are displayed in a different (wrong) order (cf screen capture)

I found that if I modify src/views/Search.vue in stac-browser, I can fix the display order, but I would prefer not to patch the browser code.
Is there something wrong with my API response, or is there a way to ensure stac-browser respects the order of the features array as returned by the API?
Thanks for your help!

[m-mohr]

@jteulade Thanks for the report. This looks like a bug and should be fixed now. Please let me know if this also works for you.

[jteulade]

It works. Thanks a lot !