redhat-developer / redhat-developer/vscode-java
Inconsistency in line break "{}" formatting in Java with in VS Code
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.3k
- Forks
- 546
- Merge medio
- 20 h 1 min
- PR fusionados (30 d)
- 11
Descripción
In my VSC I have the extension called "Language support for java(TM) by red hat". The typical one that all of us who do Java have and this is self-evident. The formatter of said extension does not format correctly. Surely the formatting is taken from LLVM so there is some error or even some incorrect syntax when formatting
When I format in VSC this example code with java or java spring boot:
❌Incorrect - If I format like this, it leaves it like this
This happens on both the opening "{" and the ending "}". It seems that the extra space has no influence since the format accepts both together and extra spacing. When the correct one is the second one with the extra spacing.
| Incorrect | Preview |
|---|---|
| ❌ | ![]() |
| ✅ | Also say the formatting of the extension also leaves it like this if the code is like this.![]() |
3 incorrect formats accepted by the formatter have been shown. Therefore, if there is any code "in that format", the formatter will leave it that way. Only the correct one is the last one or the one made by Eclipse.
This doesn't make much sense since the code is stuck above or below or even between the curly braces "{}".
This way of formatting is not expected for those of us who work with Java. Eclipse does well in this regard.
✅ correct - This is how Eclipse does it. It doesn't matter how messy the code is. It will leave it like this:
| Correct | Preview |
|---|---|
| ✅ | ![]() |
I have tried countless things, none of them worked.
This has worked since 2007 in eclipse. We are in 2024. As an example of a good format:

How do you solve this problem and get the correct form, like correct or equal to eclipse?
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Reproduce el comportamiento de formato de llaves y saltos de línea en la Java VS Code extension usando los ejemplos y las capturas de pantalla del informe, y después compara la salida con Eclipse. Rastrea el comportamiento del formatter desde el punto de entrada del formateo de Java de la extensión y determina si la discrepancia se debe a la configuración o a la implementación. Se considera terminado cuando los diseños indicados se normalicen al resultado esperado al estilo de Eclipse.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java, vscode
- Área
- tooling
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100

