1
1
# Contributing
2
2
3
- Thanks for your interest in contributing to 🏁 React Final Form! Please take a
4
- moment to review this document ** before submitting a pull request** .
3
+ Thanks for your interest in contributing to 🏁 React Final Form Arrays ! Please
4
+ take a moment to review this document ** before submitting a pull request** .
5
5
6
6
We are open to, and grateful for, any contributions made by the community.
7
7
8
8
## Reporting issues and asking questions
9
9
10
10
Before opening an issue, please search the
11
- [ issue tracker] ( https://github.com/erikras/react-final-form/issues ) to make sure
12
- your issue hasn’t already been reported.
11
+ [ issue tracker] ( https://github.com/erikras/react-final-form-arrays /issues ) to
12
+ make sure your issue hasn’t already been reported.
13
13
14
- ** We use the issue tracker to keep track of bugs and improvements** to 🏁 Final
15
- Form itself, its examples, and the documentation. We encourage you to open
16
- issues to discuss improvements, architecture, internal implementation, etc. If a
17
- topic has been discussed before, we will ask you to join the previous
14
+ ** We use the issue tracker to keep track of bugs and improvements** to 🏁 React
15
+ Final Form Arrays itself, its examples, and the documentation. We encourage you
16
+ to open issues to discuss improvements, architecture, internal implementation,
17
+ etc. If a topic has been discussed before, we will ask you to join the previous
18
18
discussion.
19
19
20
20
For support or usage questions, please search and ask on
21
- [ StackOverflow with a ` react-final-form ` tag] ( https://stackoverflow.com/questions/tagged/react-final-form ) .
21
+ [ StackOverflow with a ` react-final-form-arrays ` tag] ( https://stackoverflow.com/questions/tagged/react-final-form-arrays ) .
22
22
We ask you to do this because StackOverflow has a much better job at keeping
23
23
popular questions visible. Unfortunately good answers get lost and outdated on
24
24
GitHub.
@@ -34,8 +34,8 @@ request.**
34
34
It's never a fun experience to have your pull request declined after investing a
35
35
lot of time and effort into a new feature. To avoid this from happening, we
36
36
request that contributors create
37
- [ an issue] ( https://github.com/erikras/react-final-form/issues ) to first discuss
38
- any significant new features.
37
+ [ an issue] ( https://github.com/erikras/react-final-form-arrays /issues ) to first
38
+ discuss any significant new features.
39
39
40
40
Please try to keep your pull request focused in scope and avoid including
41
41
unrelated commits.
@@ -52,7 +52,7 @@ npm run precommit
52
52
## Coding standards
53
53
54
54
Our code formatting rules are defined in
55
- [ .eslintrc] ( https://github.com/erikras/react-final-form/blob/master/.eslintrc ) .
55
+ [ .eslintrc] ( https://github.com/erikras/react-final-form-arrays /blob/master/.eslintrc ) .
56
56
You can check your code against these standards by running:
57
57
58
58
``` sh
@@ -74,4 +74,4 @@ npm test
74
74
```
75
75
76
76
Please ensure that the tests are passing when submitting a pull request. If
77
- you're adding new features to 🏁 React Final Form, please include tests.
77
+ you're adding new features to 🏁 React Final Form Arrays , please include tests.
0 commit comments