- 🇨🇦Canada sagesolutions
I agree, config should be saved in the configuration, not in the state. This will be helpful for importing and exporting across environments.
How is the node_auto_expire configuration managed? I configured the expiration settings for my basic article content type but I don't find a way to export the configuration (I looked in node_auto_expire.settings as well in the basic article content type configuration).
As per the code, it seems using the states API instead of config API to handle the config.
Should we have the entire module config in a unique config file (simple) or should we move to something like scheduler (configure only the generic settings - messages body, bcc - in the module settings and the per content type settings part of the content type edit form).
Active
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I agree, config should be saved in the configuration, not in the state. This will be helpful for importing and exporting across environments.