Hi Steffen, On Wed, 2024-05-22 at 13:54 +0000, Steffen Van wrote: > Hi everyone, > > I would like to suggest that we introduce a code formatter in Oak. > Having a formatter will make the code easier to read and keep the > whole codebase more maintainable. Especially for new people. > > I'm not picky about which particular formatter we use — whether it's > Google's java-format, spotless, or whatever. I’m not particularly > picky about one particular, just that there is one. Most, if not all, > major open-source projects enforce a strict code-style for a good > reason. I think we should do the same.
We recently added a code formatter to Sling, here's a reference to how we did it https://issues.apache.org/jira/browse/SLING-12186 Of course, we have a different setup - hundreds of small repos - so what worked for us might not be best for Oak. Thanks, Robert
