Geocode LocationInput: Compatibility with Geocoder 3

Created on 16 April 2019, about 5 years ago
Updated 23 February 2023, over 1 year ago

Hello,

I've done some research into location searches + search_api and came to use

  • geocoder, in particular 3.x-dev
  • geofield
  • search_api
  • search_api_solr
  • facets

.. and of course search_api_location.

I would have liked to use geolocation (but i need facets, therefore need search_api,etc..) instead of geocoder/geofield/search_api_location but it seems the search_api_solr integration for geolcation is currently in the works.

In particular I needed the exposed proximity filter.

So, here you go.

πŸ“Œ Task
Status

Needs review

Version

1.0

Component

Code

Created by

πŸ‡¦πŸ‡ΉAustria vierlex

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Rerolling #15 to 8.x-1.0-alpha3. Updated service usages given the new geocoderProviderStorage instance variable. Removed the unused instance variable geocoderConfig and its associated service argument.

  • While making #21 I noticed Geocode::getParsedInput() had its logic changed for when it throws the InvalidArgumentException. I'm changing it back to how it is in the dev branch because it also matches how every other LocationInputPluginBase implements the logic: throw the exception if $input['value'] (or lat and lng) are empty. See Map.php and Raw.php.

    I reverted two tests to continue testing for that logic. I added one more test to match the ones #15 had added. I'm basing these tests off of the ones in RawTest.php.

Production build 0.69.0 2024