chore: Upgrade to flutter_map 8.0.0 and Dart 3.6.0 #84
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I haven't reviewed the changes in depth, but I haven't run into any issues testing this PR with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Flutter Map version 8 introduces significant internal changes aimed at enhancing performance by reducing type casting. A key modification is the migration from using Point to Offset and from Bounds to Rect. These changes streamline the codebase and improve efficiency.
To align with these updates, this pull request focuses on updating the library to adhere to the new standards set by Flutter Map v8. The primary goal is to refactor the codebase to utilize Offset and Rect where appropriate, replacing the previous usage of Point and Bounds. This transition not only aligns the library with the latest practices but also contributes to improved performance and code clarity.
By adopting these new patterns, we aim to enhance the library's performance and maintainability, ensuring compatibility with Flutter Map v8's optimized architecture.