Tom van Neerijnen

I came here to ask the exact same question as @xiaosansiji . I've got the below code example that deletes a node on click, changing the graph like when @xiaosansiji...

super ghetto workaround with a dependency on `lodash.isEqual`: ``` class FG extends ForceGraph { componentDidUpdate(prevProps, prevState) { var prevNodes = prevProps.children[0].map((c) => c.key); var prevLinks = prevProps.children[1].map((c) => c.key); var...

This change is in njs v0.7.7, yes? A quick glance suggests that 569292e0a74f2b1ec09566f3329f82bdd0d58e87 is indeed in that tag, so I'm assuming yes, in which case it is still not working...

so, changing the last few lines of my example like so? ``` const newFlags = { flush: flags.flush, last: flags.last, from_upstream: false, // I tried this as true also }...

with your patch i can now send traffic in both directions from any one directions callback, which enables the bi-directional handshakes I have in my original sequence diagram, it worked...

@mfaradzheva-hubble the issue occurs before onclick fires. at the point that the link is rendered onto the page, but before a click event, it is already wrong, you can see...

For anyone else hitting this issue, installing `expo-dev-client` fixed this without any of the workarounds mentioned above.

for anyone else landing here when looking for this error that @davidpdrsn encountered: > This fails with > > ``` > thread 'main' panicked at 'called `Result::unwrap()` on an `Err`...