By convention, Java API documentation comments don't follow the simple indentation nesting rules, but rather line up each line with the opening indentation + an additional space + an asterisk + a further space + some comment text (optional):
/**
* Blah
* Blah
* Blah
*/
public class ThingAMaBob {}
Could we inform eclint to handle *.java sources better, so that EditorConfig rules for indentation don't clash with JavaDoc conventions?
As a workaround, I can set the indentation to a single space, but that's not really good.
By convention, Java API documentation comments don't follow the simple indentation nesting rules, but rather line up each line with the opening indentation + an additional space + an asterisk + a further space + some comment text (optional):
Could we inform eclint to handle
*.java
sources better, so that EditorConfig rules for indentation don't clash with JavaDoc conventions?As a workaround, I can set the indentation to a single space, but that's not really good.