Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prepare deps for d3v6 #171

Closed
wants to merge 12 commits into from
Closed

prepare deps for d3v6 #171

wants to merge 12 commits into from

Conversation

Fil
Copy link
Member

@Fil Fil commented Jul 27, 2020

Note: because of the breaking changes in #81 (which impacts #17), #167 (and partly #45) this branch is "maximalist", and should be published as d3-force@3

The alternative option is to have a minimalist PR with almost no code change (ie only f429ab1 and #160), that we can keep as v2.

Fil and others added 12 commits July 27, 2020 12:18
fixes #121.(maybe)

do we need to expose jiggle(seed) so people could set the seed? (I don't think so)
Currently, the radial force...

    d3.forceRadial(radius[, x][, y])

... allows only numbers to the `x` and `y` positions:

> If x is specified, sets the x-coordinate of the circle center to the specified number and returns this force.

This proposed change allows passing functions to `radial.x()` and `radial.y()`, using the same pattern of other forces. Here is the working demo: https://bl.ocks.org/anonymous/0685343afe4675a022403be8728bc7c4/7dda06727201c128b9ff820b24c2c955e655436d
@Fil
Copy link
Member Author

Fil commented Jul 28, 2020

Split this PR into #172 (minimalist, d3-force@2) and #173 (includes breaking changes, d3-force@3)

@Fil Fil closed this Jul 28, 2020
@Fil Fil deleted the d3v6 branch July 28, 2020 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

d3.forceCenter should have an alpha parameter. Rethink automatic starting of simulations?
2 participants