Saving component configuration info as config files

[argiepiano]

Hello! I'm pretty new to webform (never used it in Drupal, always leaned toward EntityForm). I'm noticing that all the configuration information for components, conditionals and roles is saved in the database. Given the approach to saving config info as json config files in Backdrop, I'm wondering if it would be a good idea to migrate all that config info to files? I'm finding myself having to dump the database back and forth between production and development for any changes involving webform components, etc. (which often implies putting the site on maintenance to avoid changes while I'm updating things).

I know this is a big task. I may be able to help in a couple of months. I'd love to hear your thoughts. Thank you for considering.

[herbdool]

An interesting idea. I'm not opposed to it but it would have to be done carefully. All this configuration is per node and nodes only exist in the database, not in config. So it's possible for someone to delete a node and the configuration would be left behind. Or sync the config from staging where the node exists to live where it doesn't exist. Or, where the node ID is actually for a different content type altogether. So we'd have to think about how to deal with those cases.

[yorkshire-pudding]

@argiepiano @herbdool - please note that Webform Share provides the ability, albeit manually, to transfer webform config between environments. I've converted this module to use JSON rather than a PHP array so it may be that this could provide a basis to work from.