-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] enable all error-prone check #2225
Comments
@justinmclean I submit an EPIC to trace enable all |
If you enable all checks, we'll get a lot of failures. It would be better to add all (or most) passing checks in one issue and then raise an issue for each failing check one by one. |
@coolderli I think I've also created a similar issue to introduce errorprone to improve the code. I think it is a good start, really appreciated. We can fix the issue one by one to improve the quality of codes. |
@coolderli How many issues are we left to achieve this epic issue? |
@jerryshao At lease 10+. Do you have any suggestions?
|
I have no specific suggestion. We can do it one by one. I just want to know how many policies we still left, I plan to target this to 0.5.0, so hopes we can get it done before release. |
@jerryshao I got it. Due to my recent exam preparation, the speed may be slower. After this weekend, I will have more time to participate, which will speed up the process. I think I should be able to complete it in March. |
@coolderli would you please create all the subtasks about this? So that other people who have spare time can help you to achieve this.
|
@jerryshao I'm sorry about this epic can't finish before 0.5 release. But I think there is still some error-prone we can add. So I want to continue this work in 0.6. But I think I may not add all of them, because some of error-prone like Before 0.5 release, I'd like to submit a MR to exclude some error-prone that not supported for now and enable the remaining . So we can clearly see how far we are from completing this task and what we really need. What do you think? |
Sure, thanks a lot. |
Describe the proposal
In #1746 we introduce an error-prone plugin to validate code quality. But only enable the
@FormatMethhod
check. In this epic, we will enable all error-prone checks.Task list
The text was updated successfully, but these errors were encountered: