Compare with Automatic Configuration Form module

I'm not sure if I should answer at https://www.drupal.org/project/auto_config_form/issues/3518655 🌱 Compare with Schema Based Config Forms module Active or at https://www.drupal.org/project/schema_based_config_forms/issues/3518654 🌱 Compare with Automatic Configuration Form module Active , so I'll do both. :)

I'm more than happy to collaborate. Mine is older, but his looks more feature-rich. I think my module's name (Automatic Configuration Form) is more discoverable, and his module's name (Schema Based Config Forms) is more technically correct (although it should be Schema-based Config Forms to be grammatically correct). So if we merge, I'm not sure under which name we should continue.

Comparison of usage:

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

Yeah, both modules look very similar, but the approach and the structure of the "schema_based_config_forms" seems more general and flexible.

Actually, I found first the "auto_config_form" module and started to use it, but it missed support for many field types and other base features, so I implemented several MRs to improve it:
https://www.drupal.org/project/auto_config_form/issues/3515438 ✨ Adding descriptions to the form fields from schema Active
https://www.drupal.org/project/auto_config_form/issues/3519037 ✨ Add support for groups of config values Active
https://www.drupal.org/project/auto_config_form/issues/3519202 ✨ Expose general constraints to the form elements Active
https://www.drupal.org/project/auto_config_form/issues/3519101 ✨ Use parent's submitForm function directly Active

And now - analyzing the "schema_based_config_forms" and see that it is much more flexible to extend.

So, I want to invest my time into adding new features, but not sure which module to choose as the source.

The current module has a crucial blocker 📌 Automated Drupal 11 compatibility fixes for schema_based_config_forms Needs review that blocks it from easily install on Drupal 11.x, and the fix is easy, but we can't merge it without the maintainer.

So, if the maintainer of this module is ready to review and accept MRs from me, I can start extending and prepare MRs.

Also, found this module https://www.drupal.org/project/lazy_config_form → as similar :) But looks that it is abandoned.

I'll post here since it has more comments in thread.

Also happy to collaborate!

At some point I need to make time to compare the two more closely.

Sorry guys, but after analyzing both modules, I decided to go deeper and create the same approach not only for configuration forms, but for any Drupal forms.

For example, if we create a custom block with settings, we have to describe the schema for it's configuration. But it is actually not the configuration form, but just a regular form that should form the settings array for the block.

And even if you want to create just a custom form, you probably want not to create just the form design, but create a page which give you the structured input from the user. For that case, describing a custom schema looks a good and convenient way too, than managing the $form PHP array in the code. And you can include any metadata and validation directly to the schema.

So, I decided to rewrite the approach from scratch, and published this idea as a separate module with a more general name: https://www.drupal.org/project/schema_form → - "Schema Form".

For now, it's just a first draft dev version, but I will try to find time to make it more mature and stable, and publish the release.

So, could I ask some feedback from you about this idea and the general implementation approach?

And if you like, you can join the development of this module as maintainers too, I'm happy to cooperate!