Skip to content

fix: fixed issue on MarkerComposable #701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 18, 2025

Conversation

kikoso
Copy link
Collaborator

@kikoso kikoso commented Apr 10, 2025

This PR fixes an issue that was not properly done on the MarkerComposable, and that was probably introducing some performance issues (not all the problems we had were attributable to it, but certainly a percentage of them).

The main issue is that we have been measuring the view after drawing it. The procedure should have been measure and layout, then draw.

The fakeCanvas was also unnecessary, since applyCanvas creates one.

So overall, this should improve performance a bit.

@googlemaps-bot
Copy link
Contributor

Code Coverage

There is no coverage information present for the Files changed

@kikoso kikoso marked this pull request as ready for review April 14, 2025 09:17
@dkhawk dkhawk merged commit 0c51438 into main Apr 18, 2025
13 checks passed
@dkhawk dkhawk deleted the fix/performance_in_marker_composable branch April 18, 2025 16:47
googlemaps-bot pushed a commit that referenced this pull request Apr 18, 2025
## [6.5.3](v6.5.2...v6.5.3) (2025-04-18)

### Bug Fixes

* fixed issue on MarkerComposable ([#701](#701)) ([0c51438](0c51438))
@googlemaps-bot
Copy link
Contributor

🎉 This PR is included in version 6.5.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants