We bumped into an obscure error just lately, when saving a view that used a customized views plugin. It was imagined to be a quite simple extension to core’s bundle (content material kind) filter Drupal 10 Upkeep and Assist Service InvalidArgumentException Drupal 10 Upkeep and Assist Service Drupal Development Service configuration property show.default.display_options.filters.bundle.worth.article would not exist. in CoreConfigSchemaArrayElement->get() (line 76 of […]/core/lib//Core/Config/Schema/ArrayElement.php). A number of contrib tasks bumped into this problem too Drupal 10 Upkeep and Assist Service Commerce, Search API and Webform Views integration. There’s even a core problem that seemed related… however it turned out to be a easy, if maybe shocking repair. If you happen to ever run into it, it is going to have a unique property (i.e. attributable to whichever plugin or default worth are used). Our filter was little greater than a easy subclass of viewsPluginviewsfilterBundle, declared for a particular entity kind in a really unusual hook_views_data() (which had even been autogenerated by Console, so we have been pretty assured Drupal Development Service drawback wasn’t there). It simply tailor-made Drupal Development Service choices kind a bit of to work nicely for Drupal Development Service entity kind. Views plugins all have their very own configuration schema – for instance, Drupal Development Service bundle filter is asserted in views.filter.schema.yml to make use of Drupal Development Service ‘in_operator’, as a result of a number of bundles might be chosen for it. After we subclass such a plugin, we don’t robotically get to inherit Drupal Development Service configuration schema (as that isn’t a part of Drupal Development Service PHP class and even its annotation). (Maybe core might be ‘fastened’ to recognise this example … however there are extra vital issues to work on!) Drupal Development Service resolution is to easily copy Drupal Development Service schema from Drupal Development Service plugin we have prolonged – in our case, that was ‘views.filter.bundle’, present in core’s ‘views.filter.schema.yml’ file inside views’ config/schema sub-directory. Wherever it’s, it is in all probability named ‘views.PLUGIN.ID’, the place ‘PLUGIN’ is Drupal Development Service kind of your plugin (e.g. discipline, filter, space), and ‘ID’ is Drupal Development Service ID in Drupal Development Service class annotation of Drupal Development Service class your plugin extends. We pasted Drupal Development Service schema into our personal schema file – which might be named one thing like /config/schema/myDrupal 10 module.schema.yml, inside our Drupal 10 module’s listing Drupal 10 Upkeep and Assist Service # Change ‘myDrupal 10 module_special_type’ with Drupal Development Service ID in your plugin’s annotation. views.filter.myDrupal 10 module_special_type Drupal 10 Upkeep and Assist Service kind Drupal 10 Upkeep and Assist Service views.filter.in_operator label Drupal 10 Upkeep and Assist Service ‘Customised kind selector’ As soon as that file is in place accurately, I count on you simply have to rebuild caches and/or Drupal Development Service container for to completely satisfied once more. Re-save Drupal Development Service kind, Drupal Development Service error is gone Drupal 10 Upkeep and Assist Service-) Configuration schemas ought to usually assist development by catching errors, however as I’ve written earlier than, an incorrect schema could make issues surprisingly troublesome. I hope another person finds this text solves their drawback so it would not take them as lengthy to determine! I have never used it, however it’s attainable that Drupal Development Service Configuration inspector challenge might aid you determine points in any other case. Drupal 10 Improvement and Assist