Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change. If this is a breaking change, specify explicitly which APIs have been changed.
Before you create this PR confirm that it meets all requirements listed below by checking the
relevant checkboxes ([x]
). This will ensure a smooth and quick review process.
- The title of my PR starts with a Conventional Commit prefix (
fix:
,feat:
,docs:
etc). - I have read the Contributor Guide and followed the process outlined for submitting PRs.
- I have updated/added tests for ALL new/updated/fixed functionality.
- I have updated/added relevant documentation in
docs
and added dartdoc comments with///
. - I have updated/added relevant examples in
examples
.
Does your PR require Flame users to manually update their apps to accommodate your change?
- Yes, this is a breaking change. (Indicate it in the Conventional Commit prefix with a
!
, e.g.feat!:
,fix!:
). - No, this is not a breaking change.
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate which of these issues are resolved or fixed by this PR, i.e. Fixes #xxxx