fix: #3622905 Add schema for nested Geocoder Field geocode settings

Nick Hoperequested to merge
issue/geocoder-3622905:3622905-missing-schema-for into 8.x-4.x

Issue

Issue #3622905

Summary

The Geocoder Field module stores forward-geocoding settings below a nested geocode key, but the configuration schema does not define that mapping.

Proposed resolution

Add schema definitions for:

  • geocode.field
  • geocode.delta_handling

The existing top-level mappings remain unchanged because they are used by the current field configuration structure and reverse-geocoding configuration.

Testing

  • Verified the YAML diff with git diff --check.
  • Validated active Drupal configuration with the completed schema; no schema violations remain.

AI assistance disclosure: This merge-request description and implementation were prepared with assistance from an AI tool and reviewed by the contributor.

Merge request reports