Community updates are welcome!
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Adding new features
- Supporting new Language Runtimes
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can. Example stackoverflow question includes sample code that anyone with a base R setup can run to reproduce what I was seeing
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
People love thorough bug reports. I'm not even kidding.
- 2 spaces for indentation rather than tabs
- You can try running
npm run lint
for style unification
By contributing, you agree that your contributions will be licensed under its MIT License.