Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

People were trying to get the broken behavior fixed. I was more in the camp of simply removing the offending rule. But, contrary to your claim above, they did already have some config options.

Ultimately, the solution is to use Biome or another formatter instead, but many devs have Prettier forced on them at work.



Broken is subjective for this case. Some people like choice A and others want B - neither is broken.


Oh, for sure. If you don't want to live with the decisions from the project whose goal is not letting you make your own decisions, you should use something with a different goal. There is a reason most of those projects grow a bit and then die.

What you don't do is insist the developer adds the option. Even if you feel like the developer is more approachable than your boss.


In the hundreds of people who interacted on that thread, I don’t think a single person insisted that the dev do anything.

It’s a dishonest characterization of the issue thread to imply that it was its nature. People shared discussed the problem with the tool’s behavior, shared examples and motivations.

Prettier’s (IMO wrong) decision was theirs to make but the response was also gratuitously smug.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: