Problem/Motivation

Saving a View using the geofield_google_map Views style can report config schema errors for some style options in Drupal 11.

This appears to be a follow-up to #3295400: Missing schema for geofield_google_map views style configuration. The main Views style schema exists, but some saved settings still do not match the current schema.

Steps to reproduce

  1. Use Drupal 11 with Geofield Map 11.1.9.
  2. Create or edit a View using the geofield_google_map style.
  3. Configure a Geofield data source.
  4. Use the Entity Type - Image Select map theming plugin.
  5. Save the View.

The View may report schema errors such as:

  • style.options.data_source is a string but the schema expects a sequence.
  • style.options.map_marker_and_infowindow.theming.geofieldmap_entity_type_url.values.* is missing schema.
  • style.options.map_marker_and_infowindow.theming.geofieldmap_entity_type_url.id is missing schema.
  • style.options.map_marker_and_infowindow.theming.geofieldmap_entity_type_url.description is missing schema.

Proposed resolution

Update geofield_map.style.schema.yml so it matches the saved configuration shape for the Views style settings.

Remaining tasks

  • Add a merge request.
  • Review/test the schema changes.

User interface changes

None.

API changes

None.

Data model changes

None.

Issue fork geofield_map-3591145

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

nick hope created an issue. See original summary.

nick hope opened merge request !34

nick hope’s picture

nick hope commented
Assigned: nick hope » Unassigned
Status: Active » Needs review

I added MR !34.

I tested the MR locally on Drupal 11.3.9 with Geofield Map 11.1.9. Before the change, saving a View using the geofield_google_map style with Entity Type - Image Select theming produced schema warnings for data_source and geofieldmap_entity_type_url settings.

After applying the MR diff as a Composer patch, rebuilding caches, and saving the View again, the schema warnings disappeared. A config schema validation check for the affected View also returned no violations.