Add “movecancelled” event to Map
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
It’s really difficult to figure out at the application level when a map move initiated with fitBounds(), flyTo(), etc. has been cancelled by a click on the map. Currently the click event is fired after the moveend event, which complicates things even further because it can’t be guessed if the map is moving (isMoving() returns false inside the click event). So to filter out that click from, let’s say, selecting a symbol, a lot of logic needs to be implemented.
It would be good to have an event fired when a click that cancels an animated map move is performed.
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
Start by tracing the map movement paths named in the issue, including fitBounds() and flyTo(), alongside click, moveend, and isMoving() handling. Determine where an animated move is cancelled by a map click and identify the existing event tests or event entry points. Done means the new movecancelled event reliably identifies that cancellation without changing unrelated click or moveend behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100