a2aproject/a2a-java

Code formatter/reporter

Open

#139 opened on Jun 30, 2025

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (149 forks)auto 404
enhancementgood first issuehacktoberfest

Repository metrics

Stars
 (438 stars)
PR merge metrics
 (PR metrics pending)

Description

We should have something to report on things like unused imports, trailing spaces etc.

I'm only familiar with the following ones:

  • Checkstyle from https://github.com/wildfly/wildfly. I think here the rules are a bit "old" for what we want to do here. Those are my impressions from another project I worked on, but I can't remember why.
  • Spotless, from another private project I worked on. I found this way too intrusive, forcing lots of code changes for trivial stuff. Then again I am not very familiar with it.

If anyone has some ideas that would be great.

Contributor guide

Research direction
Evaluate code formatting tools like Checkstyle and Spotless for Java, considering their intrusiveness and integration with the build system. Provide a recommendation with pros and cons.
Tech stack
java
Domain
developer experiencetooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65