This lowers the autocomplete focus boost from 40 to 15. The idea is
that, because the boost for population is 20, the focus can't possibly
override a popular city, but it can come close.
On our default dev build, no acceptance tests fail but the san francisco
autocomplete test now passes!
It's not clear if this fixes WOF venue issues yet, since the latest
build there failed :(
- created `/component` route
- broke out trimByGranularityComponent but could conceivably be combined with existing
- added `address` support to text_parser
- added `component` sanitizer wrapper
adjusted tests to account for new querying strategies, renamed all existing test fixture files to `*_original`. pointed query module to a PR for testing.
the tests removed were testing far more than was appropriate since the functionality of the individual sanitisers is tested elsewhere. in this case, the test has been reduced to just testing that all the sanitisers were actually called.
rather than wholesale converting to libpostal in one release, the decision was made to only use libpostal for /search and not /autocomplete. Until such time that libpostal can be used for parsing autocomplete queries, text_parser_autocomplete.js will contain the converter between addressit and internal parsing format.
add support for FallbackQuery and GeodisambiguationQuery from the pelias-query module. GeodisambiguationQuery is used when the text-analyzer returns a single administrative area field. FallbackQuery is used otherwise.
This was missed by me when working on https://github.com/pelias/api/pull/580, but caught by the acceptance tests!
Unfortunately it was caught after going to production.
peliasAdmin was supposed to be a parameter to the multi match view, but
instead it was being sent to the score view and ignored.
Thanks to @trescube for catching this.