What tests? There is no hyperlink, for all I know, these are just some hidden tests that the owners of the competition run on the solutions to verify them. There is no link to Prettier at all, and at a first read it’s very unclear this is what they want you to do if you aren’t already familiar with the tool they want you to recreate.
Ok, I don’t know what is more worrying, that a developer fails to find prettier on GitHub, or that a developer fails to Google it.
But I guess that if you fail this, you were probably not the target audience for the challenge.
Nobody reading about the contest in the linked page should have to rely on Google to fully understand the parameters of the contest. Whoever authored this page is lazy.
Prettier is a Javascript code formatter, so it seems the challenge is to rewrite it in Rust.
Wow, they really did not make that clear at all on the contest description.
Yeah, “pretty printer” to me means some kind of pretty output library, like for terminal applications. I’d call this a “code formatter,” but whatever.
I guess this is what happens when your community doesn’t standardize on something early on. I guess I take
cargo fmtfor granted.They say you should pass 95% of the Prettier JavaScript tests to win the price.
What tests? There is no hyperlink, for all I know, these are just some hidden tests that the owners of the competition run on the solutions to verify them. There is no link to Prettier at all, and at a first read it’s very unclear this is what they want you to do if you aren’t already familiar with the tool they want you to recreate.
Ok, I don’t know what is more worrying, that a developer fails to find prettier on GitHub, or that a developer fails to Google it. But I guess that if you fail this, you were probably not the target audience for the challenge.
Nobody reading about the contest in the linked page should have to rely on Google to fully understand the parameters of the contest. Whoever authored this page is lazy.