Commit ad72e03
Recognize Markdown Javadoc in a couple of places that were missing.
We won't treat a Markdown Javadoc comment as such unless we have recorded it explicitly when visiting the node it is attached to, in `JavaInputAstVisitor`. That was missing for package declarations (for package Javadoc in `package-info.java`) and for enum constants. When a Markdown Javadoc comment is not recognized, it is treated as a regular `//` line comment that happens to have another `/` immediately after the opening `//`. In particular, if the comment is wrapped, the wrapped line will begin with `//` rather than `///`.
PiperOrigin-RevId: 9421587101 parent 2868787 commit ad72e03
2 files changed
Lines changed: 4 additions & 4 deletions
File tree
- core/src
- main/java/com/google/googlejavaformat/java
- test/java/com/google/googlejavaformat/java
Lines changed: 2 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
353 | 353 | | |
354 | 354 | | |
355 | 355 | | |
| 356 | + | |
356 | 357 | | |
357 | 358 | | |
358 | 359 | | |
| |||
814 | 815 | | |
815 | 816 | | |
816 | 817 | | |
| 818 | + | |
817 | 819 | | |
818 | 820 | | |
819 | 821 | | |
| |||
Lines changed: 2 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
2092 | 2092 | | |
2093 | 2093 | | |
2094 | 2094 | | |
2095 | | - | |
2096 | 2095 | | |
2097 | 2096 | | |
2098 | 2097 | | |
2099 | 2098 | | |
2100 | | - | |
| 2099 | + | |
2101 | 2100 | | |
2102 | 2101 | | |
2103 | 2102 | | |
| |||
2114 | 2113 | | |
2115 | 2114 | | |
2116 | 2115 | | |
2117 | | - | |
2118 | 2116 | | |
2119 | 2117 | | |
2120 | 2118 | | |
2121 | | - | |
| 2119 | + | |
2122 | 2120 | | |
2123 | 2121 | | |
2124 | 2122 | | |
| |||
0 commit comments