Currently an exported Index wil list all field instances(field.field.*) as dependencies. This is wrong since that means there will be fields that might not exist in another site where the config is being imported into due to the fact that the entity bundles might be different and it would prevent the index to being imported.

Instead of field instances the config should rely only on field definitions(field.storage.*).

Comments

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented
Issue summary: View changes
drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
CreditAttribution: drunken monkey commented
Priority: Minor » Normal

Seems to make sense, yes. We don't care at all about bundles internally (or, after #2471669: Views should show the view mode for each bundle as view modes are configured per bundle, only for view modes), so having the bundles listed as dependencies (indirectly) doesn't seem to make sense if there's a viable alternative.
Thanks for reporting!

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
CreditAttribution: drunken monkey as a volunteer commented
Status: Active » Closed (duplicate)

This will now be fixed in #2541206: Consider field storage dependency removal on Index, it seems.