| 1 | <!-- |
| 2 | Thanks for submitting a pull request! |
| 3 | We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory. |
| 4 | |
| 5 | Before submitting a pull request, please make sure the following is done: |
| 6 | |
| 7 | 1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`. |
| 8 | 2. Run `yarn` in the repository root. |
| 9 | 3. If you've fixed a bug or added code that should be tested, add tests! |
| 10 | 4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development. |
| 11 | 5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`. |
| 12 | 6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect". |
| 13 | 7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`). |
| 14 | 8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files. |
| 15 | 9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`). |
| 16 | 10. If you haven't already, complete the CLA. |
| 17 | |
| 18 | Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html |
| 19 | --> |
| 20 | |
| 21 | ## Summary |
| 22 | |
| 23 | <!-- |
| 24 | Explain the **motivation** for making this change. What existing problem does the pull request solve? |
| 25 | --> |
| 26 | |
| 27 | ## How did you test this change? |
| 28 | |
| 29 | <!-- |
| 30 | Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface. |
| 31 | How exactly did you verify that your PR solves the issue you wanted to solve? |
| 32 | If you leave this empty, your PR will very likely be closed. |
| 33 | --> |