Currently users have to 'trust' in the configuration management system to ensure that all the required configurations of certain configuration will be tracked automatically.

The features module always included the dependencies using the legend: 'automatically detected'.

We could do the same.

The basic idea is, if users click on the checkbox of a content type, we could automatically check the checkbox for all the fields and permissions, and highlight the UI in some way to indicate that that checkbox was automcally checked to to acomplish dependencies.

Using this approach, users will have a better idea of what is going to be tracked before click on 'start tracking'.

Comments

dagmar’s picture

Oh, and if a user unckeck a checkbox that is marked as a dependency or as an option configuration, we could uncheck too the checkbox at the bottom of the screen (to proccess dependencies and optionals) to avoid include again the dependency.

dagmar’s picture

StatusFileSize
new4.69 KB

I have the 70% of the work done.

dagmar’s picture

Status: Active » Needs review
StatusFileSize
new8.11 KB
dagmar’s picture

StatusFileSize
new1.12 KB
new8.33 KB

Ok, this fix a small but ugly bug. Now when you 'uncheck' a checkbox, all the dependencies and optionals are unchecked.

dagmar’s picture

StatusFileSize
new944 bytes
new8.59 KB

Last patch. Now with a visual indicator that dependencies are being processed during the ajax call.

dagmar’s picture

Status: Needs review » Fixed

Committed & Pushed to 7.x-2.x.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.