A few miscellaneous problems that I think make sense to resolve all at once:
1. yml files in config/install have a uuid. I *think* it's normal to strip uuids from exported config provided in a module's config/install folder.
2. Because uninstalling ats does not remove its configuration from the system, the module cannot be reenabled after disabling.
3. Because uninstalling ats does not remove its configuration from the system, the entities (content types, paragraphs, etc) are still present on the site after uninstalling
4. Uninstalling ats does not uninstall ats_candidate, so the candidate entity type is still around. I'm not sure if this is intended, but it seems weird.
1. Enable ats
2. Disable ats
3. Observe that all entities (e.g. content types, paragraph types, etc persist in the system)
4. Attempt to enable ats
5. ats cannot be enabled because all of its config already exists in active configuration.
I'm not completely confident about all of these, but this is what I think would work.
To fix issue 1 above:
- remove the uuids from the yml files
To fix issue 2 above:
- add ats as an enforced dependency in the module's config/install yml files. this ensures that the config is deleted
- delete the language.content_settings.* yml files altogether (i don't know why, but installing the module after adding ats as an enforced dependency prevents the module from being uninstalled altogether. removing these yml files does not seem to impact the module's functioning)
To fix issue 3 above:
- same as issue 2
To fix issue 4 above:
- add ats as a depdency in ats_candidate.info.yml
Needs review
1.0
Code
Quick patch to address the above issues. I'm not as familiar with the functionality, so I wouldn't completely know if I inadvertently broke something, but it looks like its working at first glance.