✄ -----------------------------------------------------------------------------
Thank you for your Pull Request! 🙏 Please make sure it follows the contribution guidelines outlined in this document and fill out the sections below. Once you're ready to submit your PR for review, please delete this section and leave only the text under the "Description" heading.
A concise description of what your PR is doing, and what potential issue it is solving. Use Github semantic linking to link the PR to an issue that must be closed once this is merged.
In depth notes about how this PR should be integrated by downstream projects. This part is mandatory, and should be
reviewed by reviewers, if the PR does NOT have the R0-Silent label. In case of a R0-Silent, it can be ignored.
In depth notes about the implementation details of your PR. This should be the main guide for reviewers to
understand your approach and effectively review it. If too long, use
<details>.
Imagine that someone who is depending on the old code wants to integrate your new code and the only information that
they get is this section. It helps to include example usage and default value here, with a diff code-block to show
possibly integration.
Include your leftover TODOs, if any, here.
- My PR includes a detailed description as outlined in the "Description" and its two subsections above.
- My PR follows the labeling requirements of this project (at minimum one label for
Trequired)- External contributors: ask maintainers to put the right label on your PR.
- I have made corresponding changes to the documentation (if applicable)
- I have added tests that prove my fix is effective or that my feature works (if applicable)
You can remove the "Checklist" section once all have been checked. Thank you for your contribution!
✄ -----------------------------------------------------------------------------