[TECH DEBT] Incomplete/undefined config schemas

[adam-vessey]

Overview of feature request

Coming out of the starter site project to replace islandora_defaults, it was noticed that there's a number of different pieces of config defined by Islandora which are not described by a schema: https://github.com/adam-vessey/islandora-starter-site/runs/8248656015?check_suite_focus=true#step:8:9

Ideally, all configuration should be described.

What kind of user is the feature intended for?
(Example user roles: Collections Manager, Developer, Systems Administrator, or User)

Of interest to developers and sys admins, generally.

What inspired the request?

What existing behavior do you want changed?

Any brand new behavior do you want to add to Islandora?

Any related open or closed issues to this feature request?

[adam-vessey]

Feel like I should highlight, but as of Drupal 9.3, the schemas are used to establish the order of properties in exported configurations, so having things fully defined should (eventually) lead to cleaner diffs with configuration changes.

[whikloj]

I'll leave this open for now to see if there are other schemas to be fixed.

But this also is bringing to light other configuration issues where variable type is not matching the configuration.

core.entity_form_display.node.islandora_object.default:content.field_linked_agent.settings.size       variable type is string but applied schema class is  Drupal\Core\TypedData\Plugin\DataType\IntegerData

and the config shows

 field_linked_agent:
    type: typed_relation_default
    weight: 3
    region: content
    settings:
      match_operator: CONTAINS
      size: '60'