Case-sensitivity and yml-keys.

[annitya]

Some of our yml-parameter keys are transformed to lowercase in appDevDebugProjectContainer.xml. The symfony2-plugin then reports parameters as missing, due to the difference in casing.

Excellent plugin by the way! :)

[Haehnchen]

can u give example lines of yaml and container file?
there also some tolower converts in the plugin that are from @adrienbrault . i think he knows why? :)

[annitya]

Yaml-file:

services:
contenttype:
class: someclass
arguments: [%importSettings%]

Snippet from appDevDebugProjectContainer.xml:

    <parameter key="importsettings" type="collection">
        <parameter key="language-code">nor-NO</parameter>
    </parameter>

Notice the difference between "importSettings" and importsettings. If I change the casing in the yml-file, the "missing-parameter"-message goes away.

[stof]

Parameter names are indeed lowercased in Symfony to make them case sensitive (which is why the common naming convention for parameters is not camelCased btw)

[annitya]

Lowercased to make them case sensitive?

[stof]

Parameter names are considered case insensitive in the DI component (service ids are case insensitive too).
to implement this in an easy way, they are stored in lowercase in the container (storing them with their original case would require reading all possible cases when looking for the array key, which is insane).

The PhpStorm plugin reads the parameters from the compiled container, so it has the lowercased names.
But it should indeed change its logic to be case insensitive when providing GoTo and completion

[annitya]

A common approach. Lowercased to make then case insensitive on compare then! :) I believe completion is lowercased, but GoTo is not. Completion looks up the already lowercased values from the xml-serialized container. GoTo uses the value directly from PhpStorm. A fix should be simple to implement! :)

[annitya]

Beautiful. Best plugin ever!