Drupal 10 support

[stephen-cox]

Issue to track any changes needed to support Drupal 10

[ekes]

Looks pretty straightforward, except the javascript, just running through that.

[ekes]

https://git.drupalcode.org/project/geo_entity/-/commit/bd08dbe22acc131d3c7a2fb16e3d3d1185397a71

[ekes]

Also needed https://git.drupalcode.org/project/geo_entity/-/blob/1.0.x/modules/geo_entity_address/js/autocomplete.js#L151 changed. This was the last required change for 10.x other improvements, not required for 10.x, could be moved to this module; or migrate to geo_entity.

[stephen-cox]

Looks like this is going to be the first module to have a major release with D10 only support.

It's not possible to install the Geocoder 4 along with the drupal/core-recommends 9.x package as specify different versions of Guzzle: https://www.drupal.org/project/geocoder/issues/3283651.

The current version 1 will need to require Geocoder 3 and a new version 2 will require Geocoder 4.

[andybroomfield]

As this is now Geo_entity, I suggest we make the profile for Drupal 10 use that instead. Does raise the question about what happens to modules that use lcoalgov_geo, I assume they will need a new release to support the new geo entity, and a migration for the data?

[stephen-cox]

Closing as we have D10 support working