Guide on creating or translating a kata in JavaScript

[hobovsky]

Something similar to #191

This thread would be used for discussions, ideas, and suggestions which would not fit into PR reviews.

[hobovsky]

I wonder if it would be worth to mention amount of JS runtimes and the fact that the newest one should always be preferred. Authors should make sure that Node 12 (?) is available, and not struggle for compatibility with Node 8.

[Steffan153]

Node 8 will be removed at some point anyways.

[kazk]

Yeah, any new kata or translation should use the latest version. Compatibility with older version is not needed.

[hobovsky]

In Tests section, I think the parts on organization (Mocha ) and assertions (Chai) are not sufficiently separated. My suggestion would be to organize it in a way similar to:

• Tests
  • Assertions library: Chai
    Abridged reference of most commonly used chai assertions...
  • Testing framework: Mocha
    • Test grouping functions
    • Dynamically generated test cases (after describe and it are presented, not before)
  • Test feedback (CW specific, so not in Chai and not in Mocha part)
  • Generating random numbers
  • ...

I am also not sure if it would not be better to swap parts on Chai and Mocha, but we can check it after we got these two separated.

[XRFXLP]

Suggestion:

Freeze the Object which are being as method for validation for solutions:
(For example: Math, Array, Function, String....)
For example there are many katas in which validation process uses String.prototype.split, but the translators or author usually forget to freeze or constantify the handler function, which led user to modify the prototype itself to pass the tests.

And I think this is not detected my anti-cheat system, because I've recently seen couple of such solution for few 1 kyu katas.