mapbox / mapbox/mapbox-maps-flutter
A few observations
Open
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 380
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Description
I'm sure there will be more, but after a week of working earnestly with this library:
- An object named ScreenCoordinate should store pixels, not latitude and longitude.
- Any object, regardless of name, storing latitude and longitude as x and y needs to instead store them as y and x.
- The MapboxMap should be able to report its visible area (e.g. screen size) in lat-lng or pixels.
- ==(Object other) => other is PointAnnotation && id == other.id, please.
- Implement OnPointAnnotationDragListener(PointAnnotation pa) so I don't have to implement my own.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the ScreenCoordinate, MapboxMap, PointAnnotation, and OnPointAnnotationDragListener entry points, then separate the five observations into independently scoped changes. Done would require agreed behavior for each request and validation for every affected API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100