Description

Currently, all attributes of map elements are taken into account when computing which one have changed and needs to be rebuilt. This causes changes in attributes that are not related to the platform (like onTap or onDragEnd) to trigger an unnecessary rebuild of the element. This is especially problematic as new instances of closures are often used in those handlers resulting in lots of unnecessary rebuilds.

This PR address that problem by ensuring attributes not related to the platform are ignored when comparing elements for change.

Related Issues

This PR reduces drastically performance problems explained in this issue:
flutter/flutter#41731

However, this is only one part of the problem, so this issue still needs some love <3

Checklist

• 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 (See [Contributor Guide]).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the [Flutter Style Guide].
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
• I updated CHANGELOG.md to add a description of the change.
• I signed the [CLA].
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.