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
Rather than the tricky route, I went for MVP; Now what I'd like to understand, is how to make these Statuses available as a Field and thereby within Views? They are being saved...
Form building question
And if I implement things in this manner, is there a parent-child ajaxian form demonstration (ala taxonomy creation)? Not sure exactly what you have in mind, but all layout settings forms are...
Form building question
@onyx. We have config_clear() that should do what you are after.
Form building question