Aiven-Open / Aiven-Open/klaw

Add Static Code Analyzers and Style Checkers for the Java parts

未關閉
#264 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
dependencies discuss Housekeeping
主要語言
Java
星號
195
分支
77
平均合併
8 天 9 小時
30 天內合併 PR
1

描述

# What is currently missing?

There are different ways to write Java (curly braces on same line vs newline, naming conventions), we should programatically decide on the way the project should be written.
Additionally, there are several known bug prone code patterns that we can automatically check and prevent before committing, making our code more secure and in turn reviews are easier to perform.

# How could this be improved?

Last time I worked on Java only codebases there was a triad of plugins to use:
- Spotless (I understand is a better alternative to Checkstyle) -- Already in the project :heavy_check_mark:
- PMD
- SpotBugs (successor of FindBugs)

First, decide on which tools to use (I propose the 3 mentioned above) and configure them with the proper defaults

# Is this a feature you would work on yourself?

* [x] I plan to open a pull request for this feature

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。