Link lines longer than 100 chars are malformed in ///
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start by reproducing the formatter output with the 100- and 101-character markdown links in /// comments shown in the issue. Trace the formatter's comment line-wrapping path, then add coverage for this boundary case if the relevant test location is found. Done means the 101-character link remains intact and all surrounding lines retain the /// prefix.
Written by the indexing model from the issue text.
Description
The first line illustrates a 100 character long line
The following are a markdown link line of 100 characters, and the next the same of 101 characters.
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890
/// [Design-doc](8901234567890123456789012345678901234567890123456789012345678901234567890123456789)
/// [Design-doc](89012345678901234567890123456789012345678901234567890123456789012345678901234567890)
The first is maintained through the formatter
The second is malformed by moving the link to a new line prefixed by //
/// [Design-doc](8901234567890123456789012345678901234567890123456789012345678901234567890123456789)
///
// [Design-doc](89012345678901234567890123456789012345678901234567890123456789012345678901234567890)
It'll do this regaurdless of /// comments before or after, so it can result in a // line in the middle of /// ones
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 936
- Avg merge
- 6m
- Merged PRs (30d)
- 3
Getting set up
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 google/google-java-format
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/google-java-format#1094 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
google/google-java-format#1450 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
google/google-java-format#1439 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
google/google-java-format#1436 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
google/google-java-format#1428 · 4 comments ·
Maintainers usually reply within 1 day
All issues in google/google-java-format
Similar issues
-
TerminalRow.mSpaceUsed (short) overflows on terminals wider than 1023 columns, crashing setCharOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
termux/termux-app#5340 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
apache/rocketmq-dashboard#5110 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 4 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
TS2502 in shipped .d.ts: `compileHighlightConfig` parameter shadows the de-aliased `Query` typeOpenbug javascript
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day