provide configurable control over code formatting
#1 Updated by Eric Faulhaber over 11 years ago
Currently, the Java anti-parser (e.g., brew.xml and related rule sets) is hard-coded to Golden Code coding standards, but customers will have their own formatting requirements. These should be configurable (means of configuration TBD). Features to consider:
- indents (number of spaces, optional hard tabs (yuck)?)
- curly brace placement (on a new line or at end of previous line?)
- maximum line length (if any)
- how to wrap long lines (e.g., whether or how to align parameters that flow from one line to the next?)
- how many blank lines between constructs
There are surely others and we may want to drop some of the above; this is just a starting point for ideas. We probably want to avoid items that will require changing the order in which the various parts of a Java class emit, as that will require changes to the rules logic, rather than just hooks to implement pre-determined parameters.
I suspect customer requirements will drive more or less effort in this area.