redhat-developer / redhat-developer/vscode-java
Inconsistency in line break "{}" formatting in Java with in VS Code
Personne n'a encore pris cette issue.
- Langage dominant
- TypeScript
- Étoiles
- 2.3k
- Forks
- 546
- Merge moyen
- 20 h 1 min
- PR mergées (30 j)
- 11
Description
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?
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Reproduisez le comportement de mise en forme des accolades et des sauts de ligne dans la Java VS Code extension à l’aide des exemples et des captures d’écran du rapport, puis comparez la sortie avec Eclipse. Suivez le comportement du formatter depuis le point d’entrée du formatage Java de l’extension et déterminez si l’écart vient de la configuration ou de l’implémentation. Le travail est terminé lorsque les mises en page signalées sont normalisées pour obtenir le résultat attendu au style Eclipse.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java, vscode
- Domaine
- tooling
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100

