Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Linebreaks in generics

未关闭
#526 13 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
java
领域
tooling

调研方向

首先,使用 formatter 复现所提供的 Java 输入,并将其输出与预期行为进行比较。跟踪类和方法泛型类型参数的格式化路径,然后为这些示例添加回归测试;完成的标准是泛型列表保持在同一行,同时现有的参数换行行为保持不变。

由索引模型根据 Issue 内容生成。

描述

In testing an upgrade to 1.6.1, we're sometimes seeing line breaks introduced into generics. Seems like this is probably a result of #512. I can see this being useful in pathological cases with extremely long generic type lists, but the issue is that we run prettier with a pretty aggressive line length limit, so we end up seeing split generics even in relatively straight-forward code samples. And it's pretty jarring when you first see it, because as far as I know, splitting generics like this isn't an idiomatic way to format Java (at least I haven't seen it in the wild before).

I tested the prettier-java upgrade on ~1,500 of our internal GitHub repos, and it definitely seemed like, in most cases, this generic splitting was hurting the code readability more than it helped. But curious to get your thoughts on how attached you are to this feature.

Prettier-Java 1.6.1

# Options (if any):

Input:

public abstract class GenericWblGeneratorWithLongName<OBJECT_TYPE, RECORD_TYPE> {

  public static <RECORD, OFFSET> PagedResult<RECORD, OFFSET> appendCustomOffsets(
    Arg arg1,
    Arg arg2
  ) {
    // implementation
  }
}

Output:

public abstract class GenericWblGeneratorWithLongName<
  OBJECT_TYPE, RECORD_TYPE
> {

  public static <
    RECORD, OFFSET
  > PagedResult<RECORD, OFFSET> appendCustomOffsets(Arg arg1, Arg arg2) {
    // implementation
  }
}

Expected behavior:

public abstract class GenericWblGeneratorWithLongName<OBJECT_TYPE, RECORD_TYPE> {

  public static <RECORD, OFFSET> PagedResult<RECORD, OFFSET> appendCustomOffsets(
    Arg arg1,
    Arg arg2
  ) {
    // implementation
  }
}
主要语言
Java
星标
1.2k
派生
123
平均合并
2 天 10 小时
30 天内合并 PR
35

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

jhipster/prettier-java 的其他 Issue

查看 jhipster/prettier-java 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。