Skip to content
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

Open
14 of 17 tasks
coolderli opened this issue Feb 17, 2024 · 11 comments
Open
14 of 17 tasks

[EPIC] enable all error-prone check #2225

coolderli opened this issue Feb 17, 2024 · 11 comments
Assignees
Labels
epic Key feature

Comments

@coolderli
Copy link
Contributor

coolderli commented Feb 17, 2024

@coolderli coolderli added the epic Key feature label Feb 17, 2024
@coolderli
Copy link
Contributor Author

@justinmclean I submit an EPIC to trace enable all error-prone checks. And I will continue to work on this. If a check changes too much, I will submit a separate PR for better code review.
Before the work starts, I want to confirm if all checks should be enabled?

@justinmclean
Copy link
Member

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.

@jerryshao
Copy link
Contributor

@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
Copy link
Contributor Author

#1876

@jerryshao
Copy link
Contributor

@coolderli How many issues are we left to achieve this epic issue?

@coolderli
Copy link
Contributor Author

@coolderli How many issues are we left to achieve this epic issue?

@jerryshao At lease 10+. Do you have any suggestions?

InlineFormatString
ReferenceEquality
ClassCanBeStatic
UnusedVariable
MissingSummary
UnusedMethod
ComparableType
MissingOverride
MutableConstantField
BadImport
UnnecessaryParentheses
ThrowIfUncheckedKnownChecked
ImmutableEnumChecker
StaticGuardedByInstance

@jerryshao
Copy link
Contributor

jerryshao commented Mar 5, 2024

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.

@coolderli
Copy link
Contributor Author

I have no specific suggestion. We can do it one by one. I just want to 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.

@jerryshao
Copy link
Contributor

@coolderli would you please create all the subtasks about this? So that other people who have spare time can help you to achieve this.

InlineFormatString
ReferenceEquality
ClassCanBeStatic
UnusedVariable
MissingSummary
UnusedMethod
ComparableType
MissingOverride
MutableConstantField
BadImport
UnnecessaryParentheses
ThrowIfUncheckedKnownChecked
ImmutableEnumChecker
StaticGuardedByInstance

@coolderli
Copy link
Contributor Author

@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 MissingSummary changing too many codes. I don't think I can finish it.

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?

@jerryshao
Copy link
Contributor

Sure, thanks a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Key feature
Projects
None yet
Development

No branches or pull requests

3 participants