Failing injector test for components registered with escaped slashes

[eimanavicius]

related to Config injector do not support escaped slashes in modules names #21

[coveralls]

Changes Unknown when pulling d97d2c2 on eimanavicius:master into * on zendframework:master*.

[weierophinney]

The installer will inject the name verbatim as it appears in the extra.zf composer configuration, which means that a subsequent install attempt will match it.

With your test case, you're essentially proposing a new scenario: an edited module list that uses different escaping from what is in the composer.json. I would expect that to fail, to be honest; you shouldn't be manipulating the escaping in your configuration files, and, if you do, there will likely be issues.

[eimanavicius]

I found this issue while working with ZF Apigility.

When you checkout the Apigility Skeleton you get modules.config.php were modules names are not escaped with backslashes.
Then you go to admin and add a new api (or do any other action that updates modules.config.php).
Your modules.config.php gets updated with all backslashes escaped.

I think that this is not only one scenarios that can introduce escaped slashes in module names.

Also when project supports short arrays and long arrays syntax, why it should not support very legal slash escaping in strings.