palantir / palantir/palantir-java-format
spotlessApply can generate results that exceed 120chars line length
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 907
- Forks
- 101
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 19
Description
What happened?
palanitr-java-format 2.0.0 reformats the following line which violates line length:
private static final TypeReference<Map<String, Object>> TYPE_REFERENCE = new TypeReference<Map<String, Object>>() {};
What did you want to happen?
it's possible to satisfy the line length with the following
private static final TypeReference<Map<String, Object>> TYPE_REFERENCE =
new TypeReference<Map<String, Object>>() {};
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.
Research direction
Reproduce the formatting behavior from the issue using palantir-java-format 2.0.0 and the shown TypeReference declaration. Trace the formatter entry point responsible for this declaration and verify the formatted result against the 120-character limit. Done means spotlessApply produces the wrapped two-line form without exceeding 120 characters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100