microsoft / microsoft/vscode-java-pack

Feature request, java language formatter selective comment text reflow

オープン
#891 コメント 6 件 リアクション 0 件 担当者 1 名 GitHub で見る

@CsCherrYY がすでに取り組んでいます。

2022年2月11日 から。

ai-triaged enhancement feature-request formatter
主要言語
TypeScript
スター
352
フォーク
166
平均マージ
17時間 47分
マージ済み PR(30日)
32

説明

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

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。