| 1 | ## :bookmark_tabs: Summary |
| 2 | |
| 3 | Brief description about the content of your PR. |
| 4 | |
| 5 | Resolves #<your issue id here> |
| 6 | |
| 7 | ## :straight_ruler: Design Decisions |
| 8 | |
| 9 | Describe the way your implementation works or what design decisions you made if applicable. |
| 10 | |
| 11 | ### :clipboard: Tasks |
| 12 | |
| 13 | Make sure you |
| 14 | |
| 15 | - [ ] :book: have read the [contribution guidelines](https://mermaid.js.org/community/contributing.html) |
| 16 | - [ ] :computer: have added necessary unit/e2e tests. |
| 17 | - [ ] :notebook: have added documentation. Make sure [`MERMAID_RELEASE_VERSION`](https://mermaid.js.org/community/contributing.html#update-documentation) is used for all new features. |
| 18 | - [ ] :butterfly: If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running `pnpm changeset` and following the prompts. Changesets that add features should be `minor` and those that fix bugs should be `patch`. Please prefix changeset messages with `feat:`, `fix:`, or `chore:`. |
| 19 | |