Currently, anytime a module adds a new configuration default, the module maintainer needs to write a hook_update_N() to merge the new default into the active set. This violates DRY by putting the default in two different places, and should not be necessary for all the same reasons hook_install() doesn't need to call schema_install().
Backdrop's update process can detect changes to the default sets and apply the changes automatically.
Recent comments
It’s really interesting that clearing out the menu_links table and reinstalling the Admin Bar module did the trick. Menu corruption is such a common headache when moving from D7 to Backdrop,...
Upgrading from Drupal 7 - problem
Restore Newsletter Subscriptions from a Dev Website In my last comment, I described a way to restore newsletter subscriptions from a database backup. The method involved directly editing...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
I am considering migrating my drupal 7 website to backdrop. Hi @seamus, I would like to offer my professional services for migration to BackdropCMS. Please connect If...
drupal 7 to backdrop migration