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
Request: Add config flag for JSX ternaries #6279
Comments
Hi! The reason for closing #4139 still stands: #4139 (comment) Have you used Prettier for a while, or are just getting started? It might be helpful to know that we've had several issues closed by the people opening them a couple of months later. After using Prettier for a while they realized that the formatting the were initially bothered by was no longer an issue. When it comes to JSX formatting, that is something that we've gone through several phases of improvements of and are quite happy with! So it is not something that we're going to change. Sorry! As you can see we have over 600 other issues to work on. So in this case I'm going to close your issue, but thanks for using Prettier! 🙇♂️ |
hi @lydell , no actually I've been using it for years, it's a great tool, but customization in some places can make it magnificent. You have a configuration I know you probably will not do anything with this issue but just wanted to show that there are some people in the community, which are not extremely happy with the decision. Also, it's quite strange that ternary operators are working as expected in JS, for example Playground from #5881. And it's not really clear for me why it was made another decision for JSX. |
@denieler see https://prettier.io/docs/en/option-philosophy.html and also check out the number of 👍 in #40 🙂 |
Hey! I was searching for the answer why my JSX ternaries look so weird and ugly and found this issue #4139, which is closed. Please guys, can you make a configuration flag to be able to opt out from this decision.
Thank you in advance!
The text was updated successfully, but these errors were encountered: