Update of Symfony standards

[stephpy]

As we can see on each symfony class, argument and parameter names are camelized.
They are only options which keep "underscore"

Just an update.

[weaverryan]

Hi Stéphane!

I guess it's not clear what we mean by "parameters". I think of dependency injection parameters (but perhaps these are "options"), which are underscore (see http://symfony.com/doc/current/reference/configuration/framework.html#csrf-protection).

What do you think of when you see "parameters"?

Thanks!

[stephpy]

Hi,
Imho "csrf_protection" is an option, imho parameters names are class properties, it's not clear and i'm may be wrong,

May it's a great idea to publish an example to be clear with everybody:

<?php
class MyClass // camelCase
{
    protected $argumentOne; // camelCase

    public function myMethod($argumentOne, $options) // camelCase
    {
        $myVariable = '...'; // camelCase
        $options = array_merge($options, array(
            'my_option' => 'value', // underscore
        ));
    }
}

[burn2delete]

+1 a good example would definitely help, or maybe i should learn better terminology :P

[stephpy]

We are sure than each vars/arguments/properties are camelCase, except array keys for options like

<?php
$options = array_merge($options, array(
    'my_option' => 'value', // underscore
));

So, Either we show an exemple of an array keys of options and say than each other cases are camelCase, or we show a complete exemple of all known cases. What's your opinion ?

[burn2delete]

+1 for all known cases, makes it easier for new Symfony users to start doing things correctly from the start. (like myself)

[weaverryan]

I'm going to close this PR, but what I think we need is just to add an example of the proper use of underscores to the main code block example that's already on this page: http://symfony.com/doc/current/contributing/code/standards.html

I think if we add that, it'll address that missing piece.

Thanks!