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.
- I read the Contributor Guide and followed the process outlined there for submitting PRs.
- My PR includes unit or integration tests for all changed/updated/fixed behaviors and are passing (See Contributor Guide).
- My PR does not decrease the code coverage, or I have a very special case and explained on the PR description why this PR decreases the coverage.
- I updated/added relevant documentation (doc comments with
///
) and updated/added examples indoc/examples
. - I have formatted my code with
flutter format
and theflutter analyze
does not report any problems. - I read and followed the Flame Style Guide.
- I have added a description of the change under
[next]
inCHANGELOG.md
. - I removed the
Draft
status, by clicking on theReady for review
button in this PR. - I am willing to follow-up on review comments in a timely manner.
Does your PR require Flame users to manually update their apps to accommodate your change?
- Yes, this is a breaking change (please indicate a breaking change in
CHANGELOG.md
). - 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.