|
| 1 | +<!-- |
| 2 | + 😀 Wonderful! Thank you for opening a pull request. |
| 3 | +
|
| 4 | + Please fill in the information below to expedite the review |
| 5 | + and (hopefully) merge of your change. |
| 6 | +--> |
| 7 | + |
| 8 | +###Description of change |
| 9 | + |
| 10 | +<!-- |
| 11 | + Please be clear and concise what the change is intended to do, |
| 12 | + why this change is needed, and how you've verified that it |
| 13 | + corrects what you intended. |
| 14 | +
|
| 15 | + In some cases it may be helpful to include the current behavior |
| 16 | + and the new behavior. |
| 17 | +
|
| 18 | + If the change is related to an open issue, you can link it here. |
| 19 | + If you include `Fixes #0000` (replacing `0000` with the issue number) |
| 20 | + when this is merged it will automatically mark the issue as fixed and |
| 21 | + close it. |
| 22 | +--> |
| 23 | + |
| 24 | +###Pull-Request Checklist |
| 25 | + |
| 26 | +<!-- |
| 27 | + Please make sure to review and check all of the following. |
| 28 | +
|
| 29 | + If an item is not applicable, you can add "N/A" to the end. |
| 30 | +--> |
| 31 | + |
| 32 | +-[ ] Code is up-to-date with the`main` branch |
| 33 | +-[ ]`npm run lint` passes with this change |
| 34 | +-[ ]`npm run test` passes with this change |
| 35 | +-[ ] This pull request links relevant issues as`Fixes #0000` |
| 36 | +-[ ] There are new or updated unit tests validating the change |
| 37 | +-[ ] Documentation has been updated to reflect this change |
| 38 | +-[ ] The new commits follow conventions outlined in the[conventional commit spec](https://www.conventionalcommits.org/en/v1.0.0/) |
| 39 | + |
| 40 | +<!-- |
| 41 | + 🎉 Thank you for contributing! |
| 42 | +--> |