microsoft / microsoft/vscode-java-pack
Feature request, java language formatter selective comment text reflow
@CsCherrYY arbeitet bereits daran.
Seit 11.2.2022.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 352
- Forks
- 166
- Ø Merge
- 17 Std. 47 Min.
- Gemergte PRs (30 T.)
- 32
Beschreibung
Suggestion
I noticed the java formatter will treat different types of comments different ways. For example, it automatically reflows text on the /* */ comments, but it doesn't have the same behavior on // comments where it will preserve even its own previous line breaks, which can get annoying. Is there perhaps a way we could do something like have it not reflow // comments at all and only reflow /* */ comments? Or perhaps even ignore // comments altogether for formatting purposes while still adjusting /* */ comments?
Use Cases
When I want to simply comment out code, but leave its indentation intact for later purposes, I like to just use the ctrl-/ shortcut, but formatting the code using alt-shift-f removes the indentations. I realize there is an extension feature to disable this behavior, but unfortunately, that also disables the text reflow in the javadoc comments as well as some other comments where I'd like the reflow to happen automatically upon formatting.
Examples
So for example, if I comment out this code:
// if (true) {
// return true;
// }
I would like that formatting to be retained. However, I'd also like it if the autoformat would automatically re-flow comments that are so long that they extend beyond the window width, and I could mark those with /* */. So for example, it would auto re-flow this sentence like this:
/*
* I would like that formatting to be retained. However, I'd also like it if the autoformat
* would automatically re-flow comments that are so long that they extend beyond the window
* width, and I could mark those with . So for example, it would re-flow this sentence like
* this:
*/
#204
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.