Some of the features of avrow are feature gated.
While making changes it's a good idea to build and
test with --all-features
flag.
cargo build --all-features
cargo test --all-features
BROWSER=firefox cargo doc --no-deps --open
When contributing to this repository, please discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
Following is a cursory guideline on how to make the process of making changes more efficient for the contributer and the maintainer.
- File an issue for the change you want to make. This way we can track the why of the change. Get consensus from community for the change.
- Clone the project and perform a fresh build. Create a branch with the naming "feature/issue-number.
- Ensure that the PR only changes the parts of code which implements/solves the issue. This includes running the linter (cargo fmt) and removing any extra spaces and any formatting that accidentally were made by the code editor in use.
- If your PR has changes that should also reflect in README.md, please update that as well.
- Document non obvious changes and the
why
of your changes if it's unclear. - If you are adding a public API, add the documentation as well.
- Increase the version numbers in Cargo.toml files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is SemVer.
- Update the CHANGELOG.md to reflect the change if applicable.
More details: https://github.vviipp.vipmunity/t/best-practices-for-pull-requests/10195