api/test at dfb36a82c634b35891589cf7fce6a5f2ee6da566 - api

History

Julian Simioni 10241047a6 fix(interpolation): Ensure proper sorting of streets with interpolated addresses In cases where several conditions are met, it is possible for results to be returned from the API that are not sorted as they were intended. These conditions are: * over 10 results total were returned from Elasticsearch * the interpolation middleware was called * not all street results end up with possible interpolated address matches, and some of those streets come before other interpolated address records, necessitating a re-sorting of the results in the interpolation middleware In these cases, the ordering of streets as defined by Elasticsearch, such as by linguistic match or distance from a focus point, will no longer be respected in the results. This is because Node.js's `Array.prototype.sort` uses an [unstable QuickSort for arrays of size 11 or greater](https://github.com/nodejs/node/blob/master/deps/v8/src/js/array.js#L670). The solution is to switch to a sorting algorithm that is always stable. This ensures that whatever ordering was specified in the Elasticsearch queries is observed, without any of that logic having to be duplicated, and then possibly conflict. Stable sorting is provided by the [stable](http://npmjs.com/stable) NPM package.		7 years ago
..
ciao	Remove other instances of Mapzen	7 years ago
unit	fix(interpolation): Ensure proper sorting of streets with interpolated addresses	7 years ago
ciao.json	ciao config	10 years ago
ciao_test_data.js	Remove all leading newlines in files	7 years ago