Missing config schema for require option

Please find a patch attached to resolve this.

Patch makes sense to me, if I'm being super pedantic there's a typo in successfull though :)

successfull = successful

Reviewed! Patch #3 fixed the issues. successfully applied on Drupal 9.5.x

Updated patch with fixed spelling as mentioned previously.

Hi, I experience another issue related to the same `require` option. The option is defined as a boolean in the `Drupal\search_api_location_views\Plugin\views\filter\SearchApiFilterLocation::defineOptions()`, when the `Drupal\views\Plugin\views\PluginBase::setOptionDefaults()` expects every option in the plugin to be an associative array that at least contains the `default` key. The patch fixes the mentioned issue and includes the patch from #7.
Warning: Trying to access array offset on value of type bool in Drupal\views\Plugin\views\PluginBase->setOptionDefaults() (line 187 of core/modules/views/src/Plugin/views/PluginBase.php).

@akrrev, indeed! I discovered the same issue.

Maybe @JeroenT can create a new alpha4 tag with the newest commits? The only additions are the readme file and the fix for the 'require' option.

Stefdewa → changed the visibility of the branch 3343987-missing-config-schema to hidden.

Stefdewa → changed the visibility of the branch 3343987-missing-config-schema to active.

rossb89 → changed the visibility of the branch 3343987-missing-config-schema to hidden.

rossb89 → changed the visibility of the branch 3343987-missing-config-schema to active.

rossb89 → changed the visibility of the branch 3343987-missing-config-schema to hidden.

Made a new MR for this as the previous branch for this ticket hadn't been setup properly.

uploading the diff of the MR here for easy usage as patch
works on 10.4.x