search

computerminds / cm_config_tools

DEPRECATED: Mirror of http://cgit.drupalcode.org/cm_config_tools
1 stars 0 forks source link

Change in order within config isn't recognised as a change #21

Open anotherjames opened 8 years ago

anotherjames commented 8 years ago

This was first noticed after https://github.com/computerminds/niquesa/commit/072f2d9bf35efc23d12aa88d7e2ac2cc319cdab4 / https://support.computerminds.co.uk/issues/40234 - and is possibly a red herring, but it didn't look like that change actually got picked up.

I'm not sure whether that's on export or import either!

Anyway, it needs testing. I think a core decision was made to ignore order within config, but perhaps views & maybe other config hasn't gone along with that, in which case this is important.

anotherjames commented 7 years ago

Boooo to views, which quite specifically uses the order of config keys. Permissions is a valid example, by the way, where order can change but should not be considered different -- but they are exported as associative arrays!

https://www.drupal.org/node/2361539

anotherjames commented 7 years ago

So testing shows this is a problem. Perhaps we need to default to order mattering (and maybe special-case certain common config types where we 'know' it doesn't matter)?

But this is a problem independent of the implicit-dependencies work.