CONTRIBUTING
We are open to, and grateful for, any contributions made by the community. By contributing to React Redux, you agree to abide by the code of conduct.
Reporting Issues and Asking Questions
Before opening an issue, please search the issue tracker to make sure your issue hasn't already been reported.
Please ask any general and implementation specific questions on Stack Overflow with a Redux tag for support.
Development
Visit the Issue tracker to find a list of open issues that need attention.
Fork, then clone the repo:
Building
Running the build
task will create both a CommonJS module-per-module build and a UMD build.
To create just a CommonJS module-per-module build:
To create just a UMD build:
Testing and Linting
To run the tests in the latest React version:
To run in explicit React versions (the number is the version, so test:16.3
will run in React version 16.3
):
To run tests in all supported React versions, 0.14
, 15
, 16.2
, 16.3
, 16.4
,
To continuously watch and run tests, run the following:
To perform linting with eslint
, run the following:
Adding a new React version for testing
To add a new version of React to test react-redux against, create a directory structure in this format for React version XX
:
So, for example, to test against React 15.4:
The package.json must include the correct versions of react
, react-dom
, react-test-renderer
and the correct enzyme adapter for the React version being used, as well as the needed create-react-class
, jest
, enzyme
versions and the jest
and scripts
sections copied verbatim like this:
getTestDeps.js
should load the version-specific enzyme adapter and test renderer (all versions newer than 0.14 use react-test-renderer
, 0.14 uses react-addons-test-utils
):
Then you can run tests against this version with:
and the new version will also be automatically included in
In addition, the new version should be added to the .travis.yml matrix list:
New Features
Please open an issue with a proposal for a new feature or refactoring before starting on the work. We don't want you to waste your efforts on a pull request that we won't want to accept.
Submitting Changes
Open a new issue in the Issue tracker.
Fork the repo.
Create a new feature branch based off the
master
branch.Make sure all tests pass and there are no linting errors.
Submit a pull request, referencing any issues it addresses.
Please try to keep your pull request focused in scope and avoid including unrelated commits.
After you have submitted your pull request, we'll try to get back to you as soon as possible. We may suggest some changes or improvements.
Thank you for contributing!
Last updated