Allow forms to be defined in three segments: schema, UI, data

Related: 🌱 Enhance config schema for richer default experiences Active .

Re #16 (I only just noticed this issue). One thing I've been doing for a number of years, inspired by Config Inspector indeed is use the schema label for the config form element title AND, where available after a delimiter split, for the config form element description.

It would be nice if schema could be extended to support description separately from label, for this kind of autogeneration of edit forms.

RE #14:

I think the biggest challenge is validation. We'd need to be able to make all our validation logic work on the client side somehow.

I'm about 6 years late to reply, but I've been a maintainer of the Clientside Validation → module. Admittedly, I haven't been active on that project for quite some time, others have taken over, but it might me a good starting point/inspiration for the validation of forms on the JS side.

Switched to MR

There are several contrib modules that allow building configuration forms directly from the schema:

• https://www.drupal.org/project/schema_form →
• https://www.drupal.org/project/auto_config_form →
• https://www.drupal.org/project/schema_based_config_forms →

They work very good and significantly decrease the amount of boilerplate that need to be written!

But the main issue is the strict format of the Drupal Schema format that misses the "description" property, which is crucial for most of the forms to provide good UI.

As a workaround, we can use the third_party_settings property that is already widely used in different parts of Drupal, so I created a feature request to add this property: ✨ Allow third_party_settings property in the Drupal Schema format to allow storing metadata and custom module-related data Active - please join ;-)