Change Details

The list of visits (see [[ https://archive.softwareheritage.org/api/1/origin/1/visits/ | example ]]) is returned oldest-visit-first and that's generally now what a user would want, especially given that one needs to go through the entire pagination to get the most recent one. The API should return visits in most-recent-first order instead. Also, we should document what the order is in the documentation (which is currently silent about the sort criteria).

The list of visits (see [[ https://archive.softwareheritage.org/api/1/origin/1/visits/ | example ]]) is returned oldest-visit-first and that's generally not what a user would want, especially given that one needs to go through the entire pagination to get the most recent one. The API should return visits in most-recent-first order instead. Also, we should document what the order is in the documentation (which is currently silent about the sort criteria).

The list of visits (see [[ https://archive.softwareheritage.org/api/1/origin/1/visits/ | example ]]) is returned oldest-visit-first and that's generally nownot what a user would want, especially given that one needs to go through the entire pagination to get the most recent one. The API should return visits in most-recent-first order instead. Also, we should document what the order is in the documentation (which is currently silent about the sort criteria).