Schema errors leaflet map formatter

Thanks for pointing this out @michael.acampora

But I cannot reproduce the schema errors that you report.

The Config Inspector reports no errors on the Leaflet Formatter schema and the corresponding configuration file:

core.entity_view_display.node.[node_type].[view_mode].yml
(I attach here an example of mine),

Indeed from your patch it looks to me that you are trying to attribute to the Leaflet Formatter properties
that are defined and set only in the Leaflet View and Leaflet Widget schemas, as you can see here:

• https://git.drupalcode.org/project/leaflet/-/blob/10.4.x/modules/leaflet...
• https://git.drupalcode.org/project/leaflet/-/blob/10.4.x/modules/leaflet...
• https://git.drupalcode.org/project/leaflet/-/blob/10.4.x/modules/leaflet...

Hence I am closing this as "Cannot Reproduce / Works as designed".

Please feel free to reopen with better and more clear evidence of the bags that you report ...

Reproducible on 10.4.x HEAD (554ab55), Drupal 11.4.6, clean standard install with only geofield and leaflet. Geofield on a content type, formatter set to Leaflet Map on a view display, save it:

Schema errors for core.entity_view_display.node.event.full with the following errors:
  content.field_geo.settings.leaflet_popup.value missing schema
  content.field_geo.settings.leaflet_popup.view_mode missing schema
  content.field_geo.settings.leaflet_markercluster.excluded missing schema
  content.field_geo.settings.geocoder.settings.set_marker missing schema

The saved display holds all four: value '', view_mode 'full', excluded false, set_marker false. LeafletDefaultFormatter::defaultSettings() is return self::getDefaultSettings() + parent::defaultSettings();, unfiltered, and the trait sets all four. The schema describes what is stored, not what is editable.

excluded was on the formatter until commit 967e253 (27 Jun 2025, #3473537), which removed excluded: {type: text, label: 'Exclude flag'} from field.formatter.settings.leaflet_formatter_default. That one is a regression.

MR !82. One difference from the patch in #1: each key is declared in the position the value is already stored in, so re-saving an existing display leaves the config byte identical. #1 declares set_marker first in geocoder.settings, which moves it on every display's next save. Both type excluded as boolean, which is right here: the formatter never builds the field select, so the value is always FALSE, and text casts it to ''.

On the MR branch: phpcs clean, phpunit 4/4, parallel-lint clean, composer validate ok. phpstan and stylelint findings are pre-existing PHP and vendored CSS.

Note #3473537 is closed (fixed) and its MR !46 targets 10.2.x and no longer applies.

thanks @luissousa21and @michael.acampora ... I was persuaded (and could reproduce).
Merged into 10.4.x branch, will be parto of next Leaflet 10.4.13 release ...