Use fx and fy when initializing nodes

[TranquilMarmot]

Fixes #350, fixes #295

Tested by setting sandbox/data/default.js to the following:

module.exports = {
    nodes: [
        {
            id: "node-1",
            fx: 100,
            fy: 100,
        },
        {
            id: "node-2",
            fx: 200,
            fy: 200,
        },
        {
            id: "node-3",
            fx: 300,
            fy: 300,
        },
    ],
    links: [
        {
            source: "node-1",
            target: "node-2",
        },
    ],
};

Before this change, node-3 would render in a different spot every time the page was refreshed.

With this change it always renders at 300,300.

[TranquilMarmot]

Some changes in this file are just from running prettier 😄

[TranquilMarmot]

In testing this locally it also seems to fix #295

[chetanladha]

@danielcaldas - Any idea when this can be merged and released? I tried with these changes in node_modules/react-d3-graph and it does fix the issue we are facing. So would like to understand when this fix will be available.

Just to give some context, we are also facing the issue #295. We have are using staticGraph=true and user can filter the graph view. When user switch back from filtered view to unfiltered view, existing nodes do not respect the given x,y position and it results in overlapping nodes.

@TranquilMarmot - is there any work-around, until this fix is released?

[TranquilMarmot]

I have not found any workarounds for this, no. I'm currently using a locally-published version of this library with a bunch of changes merged in (basically, all the open PRs against this repo 😄 )

[danielcaldas]

Hey, @TranquilMarmot thanks for the change! Looks good 👍

[danielcaldas]

fyi @piotrdelikat

[chetanladha]

Thanks @danielcaldas and @TranquilMarmot.

@danielcaldas - Is there any release planned in near future?

[danielcaldas]

There are a few more PRs in the pipeline before releasing a new version. Should still take a few weeks. Cheers!