There's a bit more to implementing Prettier than "add[ing] it as a button". Since the browser implementation requires plugins and parsers to be loaded when calling format. That could be challenging. It's not as easy as adding it to your favorite IDE.
@AdamRackis The question is not tagged as a feature-request, so it won't get found as one, even if Stack Overflow were interested in rewriting that part of their code base... There's good reason to vote to close the question as written. Please edit the question if you find value in it.
This opens up some interesting additional questions. Would you want the Prettier default configuration? If so, you would be using a tab width of 2 spaces, amongst other things.
(1) this definetly has to be optional (sometimes weird formatting matters, prettier doesnt support everything, etc.) (2) this definetly has to lazy load, as Prettier is quite a large library. And I agree that some kind of clarification would be helpful, but this definetly not unclear.
@JonasWilms it's clear that it has to do something it's not clear what or why. Specifics should be added. It's currently a vague suggestion, not a good feature request. I wouldn't be surprised if half the people who upvoted it did it for a different reason than the other half and neither actually considered the other group's motive.
I'm still not convinced there's a problem here, or at least not one that can be solved with an automated tool. Prettifying the markdown seems like an enormous waste of dev time to me, and as for actual code, there's lots of disagreement on styling (what is "wrong" indentation to you might be fine for someone else) and the people who don't bother proofreading their formatting before they post probably aren't going to even notice the button is there.
This site is intended for bugs, features, and discussion of Stack Overflow and the software that powers it. You must have an account on Stack Overflow to participate.
format. That could be challenging. It's not as easy as adding it to your favorite IDE.feature-request, so it won't get found as one, even if Stack Overflow were interested in rewriting that part of their code base... There's good reason to vote to close the question as written. Please edit the question if you find value in it.