Extra config marked as excluded in info.yml file [#2534524]

When a feature is exported the first time, many of the components are added to the "exclude" section of the info.yml file.

Not all are added. A auto-detected view was not excluded. An imag_style manually added was not excluded. Very odd.

Comments

Comment #1

mpotter CreditAttribution: mpotter commented 16 July 2015 at 13:16

Removing the exclude links from the info.yml file and then re-exporting the feature doesn't cause them to be added back again. So only an issue when initially creating.

Comment #2

16 July 2015 at 17:41

mpotter committed b60f1e4 on 8.x-3.x

Issue #2534524: Extra config marked as excluded in info.yml file

Comment #3

mpotter CreditAttribution: mpotter commented 16 July 2015 at 17:44

Status:

Active

» Fixed

Nice! Looks like D8 FormState->getValue() now uses the original key instead of requiring conversion into a "dom-friendly" clean key like in D7. In other words, special characters like . and _ are handled correctly by form API.

But, this caused all our logic in handling the edit form to break. So fixed that in commit b60f1e4.

Also fixed a regression from commit 8ee6565 to put the 'info' data back into the package so it can look at the list of excluded config. Since it wasn't ever reading the exclusion list, the fact it was adding everything to the exclusion wasn't getting noticed.