Allow filters on quadtree.find

Open
  • Is something wrong?
#19 1 comment 1 reaction 1 assignee View on GitHub

@mbostock is already working on this.

Since Jun 13, 2017.

  • #28 by @Fil — open

Assessment

This issue has not been assessed yet.

Description

I like to use an optional filter argument with the find method so that the search can return only the nearest relevant point (e.g.: the nearest red point if blue points have been temporarily hidden by a user interaction). The basic fork that works for my purposes is extremely simple; it would take slightly more work to properly handle coincident points.

Something like this is referenced in an existing pull discussion. Happy to file a pull request for just this if desired.

Dominant language
JavaScript
Stars
238
Forks
54
Avg merge
1d 13h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from d3/d3-quadtree

All issues in d3/d3-quadtree

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.