Skip to content

Maintenance: Evaluate Spotbugs rules #1808

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.

Sign up for GitHub

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

Jump to bottom
Open
1 of 2 tasks
phipag opened this issue Mar 17, 2025 · 0 comments
Open
1 of 2 tasks

Maintenance: Evaluate Spotbugs rules #1808

phipag opened this issue Mar 17, 2025 · 0 comments
Labels
governance maintenance v2 Version 2

Comments

@phipag
Copy link
Contributor

phipag commented Mar 17, 2025 •
edited
Loading

Summary

After #1788 was resolved we should evaluate all Spotbugs rules to identify which rules bring us value and which should stay suppressed. The aim should be to enable as many rules as possible and follow Java best-practices in keeping the code robust.

Why is this needed?

This helps avoid future bugs and keeps the code standard high by enforcing Java best practices through workflows.

Which area does this relate to?

No response

Solution

No response

Acknowledgment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
governance maintenance v2 Version 2
Projects
Powertools for AWS Lambda (Java)
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@phipag