Resolve "Add .editorconfig to keep coding style consistance for different IDE/Editors"
What does this MR do?
Adds default editor settings file. This allows us to have certain defaults set in our editors as developers, w/o having to worry they are set, or that others have them set.
This allows for ensuring we are adhering to linting rules further to the left in the devops life cycle.
For instance, I'd much rather have some standards applied by default, and not have to worry about them first popping up in CI. That cost for me is significant in time. Things like empty line at the end of a file has bitten me many times, and is not something I should have to think or worry about setting myself.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #16143