[JAVA-3922] Share an EditorConfig config Created: 07/Jan/21 Updated: 28/Oct/23 Resolved: 14/Jan/21 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0 |
| Type: | Task | Priority: | Trivial - P5 |
| Reporter: | Valentin Kavalenka | Assignee: | Valentin Kavalenka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Documentation Changes: | Not Needed | ||||||||||||
| Description |
|
It'd be good to use a common style for the code in the repo (what exact style we use is much less important than the universality of its application). We have at least the following options:
|
| Comments |
| Comment by Githook User [ 14/Jan/21 ] |
|
Author: {'name': 'Valentin Kovalenko', 'email': 'valentin.kovalenko@mongodb.com', 'username': 'stIncMale'}Message: Add .editorconfig (#633) IntlliJ IDEA support: https://www.jetbrains.com/help/idea/configuring-code-style.html#editorconfig
|
| Comment by Ross Lawley [ 08/Jan/21 ] |
|
This is similar in intent to JAVA-3809. The benefits of using spotless is it can be automated on the compile step in gradle to ensure that code is reformatted to the coding standard. Spotless is used to great effect in the KAFKA code base. |