refactor: Add error handling and optimize marker/camera operations #251
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.
This pull request primarily focuses on enhancing error handling and code organization in the
example/lib/pages/camera.dart
andexample/lib/pages/markers.dart
files. The most important changes include adding try-catch blocks for error handling, refactoring camera movement logic into a helper method, and improving marker management.Error Handling Enhancements:
_startNavigation
,_stopNavigation
,dispose
, andcalculateFocusCenter
methods to handle potential errors and display appropriate messages. [1] [2] [3]addMarkerToMap
,_removeMarker
,clearMarkers
,_updateSelectedMarkerWithOptions
,_toggleCustomIcon
, anddispose
to ensure robust error messages are shown. [1] [2]Code Organization Improvements:
_moveCameraWithAnimation
to reduce code duplication and improve readability. [1] [2] [3] [4] [5] [6] [7] [8]_updateMarkerProperty
to streamline the code and reduce redundancy.These changes collectively enhance the robustness and maintainability of the codebase.