Skip to content

Contributing Handbook

Johan Hargne edited this page Feb 19, 2018 · 4 revisions

So you want to contribute to the project? How lovely! Here are a few things to keep in mind when working with the project:

Linting

ESlint is used for style management. Make sure that your IDE recognizes the project's eslint config before you start developing.

Testing

This project is using jest for testing and the test specifications should be placed within the /test folder. All functionality should have it's use-cases somewhat thoroughly tested (best sentence ever, thank you very much).

Running the tests

You test the project by running npm run test. It is worth noting that ESLint will run prior to Jest to make sure that there are no linting errors in the code.

Test Coverage Thresholds

"branches": 50,
"functions": 50,
"lines": 50,
"statements": 50

Pull Requests

When you are done with your contribution, issue a pull request. There is a TravisCI setup that will run checks on each commit to make sure that the tests are looking fab, so please make sure to check that the checks are passing.

The project maintainers will then have a look at your awesome contribution as soon as possible!

Have fun

🎺 This is the most important thing of all.