-
-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent doctype case formatting #3358
Comments
Seconding this issue as I had just experienced the same while formatting my code via the CLI, and was confused about the discrepancy - what is the prettier's team's recommendation on this? ( I noticed multiple discussions on the debate between uppercase and lowercase, including this one - while my understanding is that the prettier team recommends lowercase and enforces it by default back in 2019, I wonder is this still the case now?) |
Lowercase is invalid XML. This shouldn't be difficult to resolve. |
I found the reason for this problem: it seems that the Prettier VSCode plugin version 10.4.0 uses Prettier version 2.8.8 whereas the latest version of Prettier is 3.3.2 (as of today). Prettier 2.8.8 produces |
The vscode extension resolves the local version of prettier if there is one, otherwise it falls back to 2.8.8. It is recommended that you install prettier in your project to keep the results consistent. |
Thanks! It works fine for me. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
No, I don't have a preference if the doctype is lowercase or uppercase, like the below mentions:
I really don't care. But please make it at least consistent. Now I get changes in git just because Prettier formats it inconsistently.
Prettier v10.4.0
Case 1: Prettier auto-formatting in VSCode with extension.
Input:
Output:
Case 2: Prettier CLI formatting using
bunx prettier index.html
Input:
Output:
Expected behavior:
The two tools should have the same case formatting for the doctype tag, whichever it is.
The text was updated successfully, but these errors were encountered: