Improve configuration schema and how we use it

Okay, I’ve decided to create a merge request for the “safest” change, i.e.: the one that only makes changes that maintain compatibility with Drupal 9.0, i.e.: changing certain types from string to path.

Merging the string → path changes.

Moving back to "Active" for the rest of the proposed changes

Note that part 1 of this change was released in sitemap-8.x-2.0-beta7 → ; but there are still outstanding parts of this issue to be released in the future.

From my own comment in #3465577-18: Split sitemap_book config schema from sitemap schema → :

I'm guessing that a lot of the nullable keys were the result of all plugin settings being lumped into a single array. You had to do that so one plugin could leave all the other settings as empty.

While this config improvement is going on, any unnecessary nullable properties should be removed.

Updating the issue summary: we are unblocked now, so moving to Needs Work.

I split off...

2. If we dropped support for D9 and D10.0 through 10.2, (i.e.: support only D10.3+ and D11.0+ only, we could change sitemap.settings.plugins.*.weight from type integer to weight

... into its own issue, 📌 Change sitemap.settings.plugins.*.weight from type integer to weight Postponed ; updating issue summary to say this.

mparker17 → changed the visibility of the branch 3465601-config-schema-2 to hidden.

I split off...

3. If we dropped support for D9 and D10.0 through 10.1 (i.e.: support 10.2+), we could simplify the configuration form by making use of #config_target in our main config form.

... into its own issue, 📌 Start using #config_target in SitemapSettingsForm Active ; updating the issue summary to say this.

I think that, since we've split the remaining tasks into 📌 Change sitemap.settings.plugins.*.weight from type integer to weight Postponed and 📌 Start using #config_target in SitemapSettingsForm Active , we can mark this as fixed.