Added space fixer for use statement in lambdas
merged branch andreadelfino/master (PR #50)

Commits
-------

a4ab648 Added space fixer for use statement in lambdas

Discussion
----------

Space fixer for "use" statement in lambda function

This patch cover only the following case, transform something like:
```php
$locked = $locker->handle($user, function()use($downloadable){ ...
```
in:
```php
$locked = $locker->handle($user, function() use ($downloadable) { ...
```

Hope can be useful!

---------------------------------------------------------------------------

by fabpot at 2012-05-24T11:59:04Z

Can you rebase your changes against master as there are some conflict. Thanks.

---------------------------------------------------------------------------

by andreadelfino at 2012-05-24T12:25:13Z

Rebased, should work now.

---------------------------------------------------------------------------

by nysander at 2012-05-24T12:31:22Z

Am I wrong or there is one closing parenthesis missing in those examples?

---------------------------------------------------------------------------

by stof at 2012-05-24T12:35:06Z

@nysander what is missing is the body of the function too. The closing parenthesis for the ``->handle()`` call would come only after the ``}`` which is not there either

---------------------------------------------------------------------------

by andreadelfino at 2012-05-24T12:37:06Z

Yes, cause the inner block is not involved in the fixer replacement.
I can re-edit post by adding ellipses for clarity.

---------------------------------------------------------------------------

by nysander at 2012-05-24T12:40:36Z

ok thanks for explanation

---------------------------------------------------------------------------

by fabpot at 2012-06-08T08:22:59Z

Can you squash your commits before I merge? Thanks.

---------------------------------------------------------------------------

by andreadelfino at 2012-06-08T17:23:19Z

I tried to squash my commits, I hope in the right way...

---------------------------------------------------------------------------

by adrienbrault at 2012-06-08T21:46:56Z

@andreadelfino Try this http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html

---------------------------------------------------------------------------

by stof at 2012-06-09T07:43:02Z

@andreadelfino you merged your remote branch instead of forcing the push, meaning you kept the old commits and added the squashed one.

---------------------------------------------------------------------------

by stof at 2012-06-28T20:47:16Z

@andreadelfino ping

---------------------------------------------------------------------------

by andreadelfino at 2012-06-30T10:57:44Z

I'm sorry for the latency and the wrong try, I really hope this can be the good one!
Fixed braces fixer for else if statements.
fixed composer
merged branch pylebecq/fix-braces (PR #109)

Commits
-------

65d2887 Fixed braces fixer for else if statements.

Discussion
----------

Fixed braces fixer for else if statements.

Hey there,

I found out a weird case with some "else if" statements. It is related to the braces fixer. When it encounters something like
```php
if (...)
{
    // ...
}
else if (...)
{
    // ...
}
```
It will convert it to
```
if (...) {
    // ...
} else { if (...)
    // ...
}
```

Which is totally wrong. If you have several "else if" statements, you end up with successive "else" statements, resulting in a parse error.
Fixed issue #114 "Wrong behaviour of "braces" fixer in some control statements"
more flexibility of FixCommand - dependency injection
fixed PHP warnings about unknown preg modifiers - probably due to some broken utf8 chars
merged branch mheleniak/flexibility (PR #118)

Commits
-------

631582e fixed PHP warnings about unknown preg modifiers - probably due to some broken utf8 chars
17b1767 more flexibility of FixCommand - dependency injection

Discussion
----------

More flexibility of PHP-CS-Fixer

This change allows to extend PHP-CS-Fixer and add custom fixers outside PSR scope which can solve some of current issues (fixes #93, fixes #92, also see: #105 & #55).

I also fixed PHP warning in a separate commit which sometimes were thrown (probably because of some utf8 chars).

Hope this small change can be merged.
merged branch jmfontaine/master (PR #115)

Commits
-------

84b7e54 Fixed issue #114 "Wrong behaviour of "braces" fixer in some control statements"

Discussion
----------

Fix for issue #114

This is the fix for the issue #114 I reported earlier.

It includes a unit test to show the bug and that fix is working. I haven't seen such unit test in PHP CS Fixer but I think this is a nice addition to my fix.
Fix blank line before return if used ine an if/els/else if/else context with no opening brace used
Fix if there is multiple blank line between the previous instruction and the return statement
Remove unneeded rtrim
merged branch JEDIBC/fixReturnIfNoBraces (PR #120)

Commits
-------

fb141b9 Remove unneeded rtrim
3c46626 Fix if there is multiple blank line between the previous instruction and the return statement
8912019 Fix blank line before return if used ine an if/els/else if/else context with no opening brace used

Discussion
----------

Fix blank line before return if used ine an if/els/else if/else context ...

...with no opening brace used

Like :

```
if ($foo == $bar)
    return true;
```

must remain without blank line.
Added basic Drupal code standard compatibility.