Consider a `.forces()` method that gets/sets the forces map about d3-force

[mbostock]

Hmm. Well, simulation.forces would need to return a copy, and make a defensive copy, of the map to prevent the map from being modified without force.initialize being called. And using simulation.forces to set new forces is potentially slower than simulation.force if it causes some of existing forces to be re-initialized… Also it exposes the fact that the simulation uses d3.map under the hood, which I’m not wild about.

A more conservative approach might be to just add a simulation.forces getter method which takes no arguments and returns an array of {key, value} objects representing the bound forces. It could be implemented as:

forces: function() {
  return forces.entries();
},

That seems like the most conservative approach as far as enabling inspection goes. The downside is that it’s not as easy to make bulk changes to the registered forces.

[nfcampos]

@mbostock Thanks for the reply!
Yes, the getter like you described would be enough for my needs. My need for it comes down to the way I'm thinking about the props of the force layout component, ie.

<ForceLayout
  nodes={[...]}
  forces={{
    link: forceLink(...),
    center: forceCenter(...),
  }}
/>

and the component internally takes both nodes and forces and creates the simulation. (this is why I'd need the getter, to be able to know which of the forces passed in now are new.)
I'm however not sure whether it'd be better to just accept an already configured simulation object as a prop and avoid all this.

const sim = forceSimulation()
  .nodes([...])
  .force('link', forceLink())
  .force('center', forceCenter())

<ForceLayout
  simulation={sim}
/>

do you have any opinion either way?

[Fil]

Closing due to inactivity. Note that another possibility is to create

function logger(simulation) {
  simulation.forces = new Map();
  simulation.addforce = simulation.force;
  simulation.force = (name, force) => (
    simulation.forces.set(name, force), simulation.addforce(name, force)
  );
  return simulation;
}

then call simulation = logger(d3.forceSimulation()) .force("x", …).force("collide", …)

simulation.forces will then hold the map of forces (see https://observablehq.com/d/d999cd71c09c86ef).