google / google/google-java-format

Formatter places opening """ of text block on same line as ? / : operators in ternary expressions

Aberta
#1,378 0 comentários 0 reações 0 responsáveis Ver no GitHub
Linguagem predominante
Java
Estrelas
6.2k
Forks
936
Merge médio
6min
PRs com merge (30d)
3

Descrição

### Description

`google-java-format` formats ternary expressions containing text blocks such that the opening `"""` is placed on the same line as the `?` and `:` operators. This appears to violate **Google Java Style Guide Section 4.8.9**, which states:

> The opening """ of a text block is always on a new line. That line may either follow the same indentation rules as other constructs, or it may have no indentation at all (so it starts at the left margin). The closing """ is on a new line with the same indentation as the opening """, and may be followed on the same line by further code. Each line of text in the text block is indented at least as much as the opening and closing """. (If a line is indented further, then the string literal defined by the text block will have space at the start of that line.)

The key requirement is that the `"""` must be on a new line, but the formatter places an operator (`?` or `:`) immediately before it on the same line, meaning the `"""` is no longer on the new line.

### Reproduction

```
vivek@Viveks-MacBook-Air checkstyle % cat > /tmp/TernaryBug.java << 'EOF'
class TernaryBug {
boolean flag = true;

String a = flag
? """
yes
"""
: """
no
""";
}
EOF

vivek@Viveks-MacBook-Air checkstyle % java -jar /tmp/google-java-format.jar /tmp/TernaryBug.java > /tmp/TernaryBug_formatted.java
diff -u /tmp/TernaryBug.java /tmp/TernaryBug_formatted.java
--- /tmp/TernaryBug.java 2026-04-18 18:43:21
+++ /tmp/TernaryBug_formatted.java 2026-04-18 18:43:26
@@ -1,11 +1,12 @@

class TernaryBug {
- boolean flag = true;
+ boolean flag = true;

- String a = flag
- ? """
+ String a =
+ flag
+ ? """
yes
"""
- : """
+ : """
no
""";
}

vivek@Viveks-MacBook-Air checkstyle % cat > /tmp/TernaryBug.java << 'EOF'
class TernaryBug {
boolean flag = true;

String d = flag ?
"""
yes
"""
:
"""
no
""";
}
EOF

vivek@Viveks-MacBook-Air checkstyle % java -jar /tmp/google-java-format.jar /tmp/TernaryBug.java > /tmp/TernaryBug_formatted.java
diff -u /tmp/TernaryBug.java /tmp/TernaryBug_formatted.java
--- /tmp/TernaryBug.java 2026-04-18 18:45:14
+++ /tmp/TernaryBug_formatted.java 2026-04-18 18:45:19
@@ -1,12 +1,12 @@

class TernaryBug {
- boolean flag = true;
+ boolean flag = true;

- String d = flag ?
- """
- yes
- """
- :
- """
- no
- """;
+ String d =
+ flag
+ ? """
+ yes
+ """
+ : """
+ no
+ """;
}

```

### Expected Behavior

The formatter should place the opening` """ `on its own line, separate from the `?` and `:` operators. For example:

```
class TernaryBug {
boolean flag = true;

String a =
flag
?
"""
yes
"""
:
"""
no
""";
}
```

Or any equivalent layout where `"""` is the only non-whitespace content on its starting line.

### Why This Matters

Checkstyle's TextBlockGoogleStyleFormatting check enforces the Google Java Style Guide rule that the opening """ must be on its own line. The current formatter output directly conflicts with this check, code formatted by google-java-format produces Checkstyle violations. This creates a situation where developers cannot simultaneously satisfy both the formatter and the style checker, which are both intended to enforce the same Google Java Style Guide.

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Comece formatando o arquivo fornecido /tmp/TernaryBug.java com /tmp/google-java-format.jar e compare o diff exibido. Rastreie como o formatter trata expressões ternárias que contêm blocos de texto e, em seguida, verifique se cada aspas triplas de abertura é o único conteúdo que não é espaço em branco na linha e se a saída esperada não entra mais em conflito com a verificação TextBlockGoogleStyleFormatting do Checkstyle.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
java
Domínio
tooling
Tipo de issue
Bug
Dificuldade
3/5
Tempo estimado
1-2 dias
Status de atividade
Pouca atividade
Clareza
Claramente especificada
Facilidade para iniciantes
68/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.