README has links to non-force-directed beeswarms
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- documentation
Research direction
Read the README and compare both beeswarm links with the Observable plot they reference. Decide whether the links need clearer labeling or replacement, taking into account the concern that force-directed positioning can move points from their correct positions. Done means the README no longer misleads readers about the plot; an open linked pull request indicates this work may already be underway.
Written by the indexing model from the issue text.
Description
The README has two links to a beeswarm plot on Observable: one in the text and one an image. The current version of the plot on Observable is not force directed, so perhaps it might be confusing for people who want to learn how to create a force-directed beeswarm?
I love the d3-force library but I have mixed feelings about using it for beeswarm plots because the points can be moved slightly away from their correct positions. So I'm not sure about the best way to update the README (or perhaps it's fine the way it is!)
- Dominant language
- JavaScript
- Stars
- 2k
- Forks
- 395
- Avg merge
- 5h 46m
- Merged PRs (30d)
- 1
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
- 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.
More from d3/d3-force
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
-
`README` links to deprecated notebookPossibly taken @hirehamir claimed this 1200 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
maintenance
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
assistant-ui/assistant-ui#10496 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
ai bug design good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
neomjs/neo-agent-institution#927 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gramps-project/gramps-web#1671 ·
Maintainers usually reply within 1 day
-
bug good first issue priority: P2 status: ready
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
RhinoLink-Tech/data-fabric#502 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
cline/mcp-marketplace#3708 ·