hobovsky
hobovsky
Breakdown of #5 Migrate the snippet [Random testing in JavaScript](https://github.com/codewars/codewars.com/wiki/Snippets%3A-Random-testing-in-JavaScript) from the old wiki.
Show how to set up local environment to create C kata or train on them.
Breakdown of #5 Create tutorial introducing translators to translating a kata. Link with relevant parts of documentation, for example ones related to [authoring](https://docs.codewars.com/authoring/). Location: probably https://docs.codewars.com/authoring/translation/
Breakdown of #139 Set of guidelines related to writing a new kumite. Suggested guidelines: - ...
Motivated by [this post](https://github.com/codewars/docs/pull/187#discussion_r538636116) Some authors use undocumented capabilities of test output panel to improve styling or presentation of test results, like: - console output with messages or ASCII art...
`/concepts/kata/translations.md` has some placeholders to be filled in with links to documentation which is yet to be written: - translation authoring guidelines (dedicated issue: #134 )
"Getting started" docs contain links to other areas of docs, which are not available yet. Currently these links are just placeholders marked with TODO, and they need to be filled...
We agreed that some forms should not be used. We were also advised to avoid some constructs. Maybe we could enforce them with additional linter rules? There's already rule for...
Currenlty pages describing a language supported by Codewars are quite comprehensive, but I think they could be both standardized and a bit richer. I thought about including following information: ✔️...
Please complete the following information about the package: - Package name: `org.junit.jupiter:junit-jupiter-params` - Language name: Groovy - Website: [Maven repo](https://mvnrepository.com/artifact/org.junit.jupiter/junit-jupiter-params), [JUnit manual](https://junit.org/junit5/docs/current/user-guide/#writing-tests-parameterized-tests) Following are optional, but will help us consider...