Prepare repo for open sourcing about wave HOT 5 CLOSED

In addition to points above, since tslint is deprecated, I am going to replace it with typescript-eslint as suggested in the official docs.

from wave.

Other possible improvements regarding git hooks:

• Consistent commit message format (e.g. conventional commits).
• Implement git hooks for the whole repo and add support for linting staged files other than JS - (.py, .md, .go).

@lo5 @geomodular

from wave.

Agree @mturoci - I'm fine with conventional commits as long as the [optional scope] part is not enforced.

from wave.

In order to enforce git hooks for each developer I use husky in combination with lint-staged for linting.

It works fine for ui part of repo since I have included it in package.json there. However, if we want to use it for the whole repo, I would have to create a package.json and corresponding node_modules in project root and set it all there.
Despite the fact I think project root should not be polluted with nodejs or any other language specific files other than configs, I could not find any other way around it.

Problem no. 2 is that for commit linting and markdown linting there exist npm packages, go has native linter as part of an SDK, but the problem is python one. As far as I discovered, python requires pip installing the linter locally. This would introduce requirements.txt in project root. @lo5 any idea as someone who has much broader python experience? Please also read the previous section.

from wave.

Adding .nvmrc with current LTS Node version (via @mnezh)

from wave.