🐱 First off, thanks for taking the time to contribute! 🐱
The following is a set of guidelines for contributing to fast-check and its packages. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Feel free to contribute, ask questions, report bugs and issue pull requests
Before asking questions, please double-check you can not find your answer in one of the examples provided or in the documentation of the project:
- Documentation
- Examples provided inside the project
- Examples of properties
- Example: fuzzing a REST API
If nothing answered your question, please do not hesitate to create a new issue in GitHub.
You should report bugs using create a new issue in GitHub.
In order to start playing with the code locally you must run the following set of commands:
git clone https://github.com/dubzzz/fast-check.git && cd fast-check
npm install
npm run prebuild #generate missing implementations: tuple and properties
npm run build #compile the code in ./src, build the ./lib content
Once done, everything is ready for you to start working on the code.
Code style standard is enforced by Prettier.
Once done with your development you can check it follow the recommended code style by running npm run format:check
or run autofixes with npm run format:fix
.
You should also check for linting by running npm run lint:check
.
All pull requests will trigger Travis CI builds. It ensures that the pull request follow the code style of the project and do not break existing tests.