add .editorconfig file

[gggeek]

Description

Add an editorconfig file

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I updated the documentation (see here)
• I agree that this code is used in AdminLTEBundle and will be published under the MIT license

[kevinpapst]

While I do agree with most of the settings, I I don't feel completely comfortable with the last two ones.
The trim trailing whitespace can introduce weird problems at least when editing the documentation .md files.

Probably move the last two rules under a *.php block?!

[*.php]
insert_final_newline = true
trim_trailing_whitespace = true

[gggeek]

OK.
Are you a fan of 'rebase your PRs so that they only show 1 commit', or is it ok to have many commits in your git logs?

[gggeek]

I moved the more 'aggressive' trimming and newline settings in a dedicated block, but made it apply to most file types besides php.
In my own experience, I never had troubles with that, as long as there is a minimum of discipline applied throughout the codebase (arguably, one could create even a php file where trailing whitespace is semantically important, but I am sure such practice is universally considered bad)

[kevinpapst]

OK.
Are you a fan of 'rebase your PRs so that they only show 1 commit', or is it ok to have many commits in your git logs?

I don't care, I use squash merging anyway ;-)

Regarding the rules: I want to avoid that someone pushes a PR that suddenly changes whitespaces ... you are right that it shouldn't make a difference. But this repo was forked and some of the code is pretty old and wasn't touched by myself.

For PHP files I agree that it is safe, as automatic rules via phpcs are already in place.
Conclusion 😁 please use [*.php] only for now.

[gggeek]

updated

[kevinpapst]

Thank you @gggeek 👍