incorrect formatting for a record + @DefaultValue
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java, spring
- Domain
- build-system
Research direction
Reproduce the record formatting in spring-cloud-kubernetes by running mvn compile with the shown @DefaultValue annotation, then trace the shared build and formatting configuration in spring-cloud-build. Done means the annotation is formatted consistently and a subsequent mvn compile does not produce another source change.
Written by the indexing model from the issue text.
Description
If I have a very simple record in the form:
public record TestRecord(@DefaultValue({"123", "456" }) Set<Integer> knownSecurePorts){
}
this in spring-cloud-kubernetes that uses 4.0.0-SNAPSHOT. and run mvn compile for it, it is formatted like this:
public record TestRecord(@DefaultValue( {
"123", "456" }) Set<Integer> knownSecurePorts){
}
So the next time I try to issue mvn compile, it will fail.
- Dominant language
- Shell
- Stars
- 225
- Forks
- 295
- Avg merge
- 18h 57m
- Merged PRs (30d)
- 14
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from spring-cloud/spring-cloud-build
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
documentation
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
spring-cloud/spring-cloud-build#195 · 3 comments ·
-
task
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
All issues in spring-cloud/spring-cloud-build
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·