Update vis-network to version 6

Question

Update vis-network to version 6

kovalchuk-vyacheslav opened this issue 5 years ago · comments

Current version of this package uses version 5 of vis-network. However in version 6 there are a lot of improvements which I'm not able to use now.

So can u update this package to version 6?

mkarimv · Answer 1 · Wed Dec 18 2019 22:03:48 GMT+0800 (China Standard Time)

I have the same request.

Cedric · Answer 2 · Mon Mar 30 2020 11:08:15 GMT+0800 (China Standard Time)

why no update to 7? lol

Carter Hesterman · Answer 3 · Fri May 01 2020 06:01:44 GMT+0800 (China Standard Time)

I created a fork and published it to npm with some minor bug fixes and updates in it that I plan on maintaining for my company (which relies on this library). I just updated it to v6.5.2 and everything appears to be working as expected. Upgrading to v7 had some breaking changes so I haven't implemented that one yet. If you want to give it a go, here is the link:
https://github.com/hesto2/react-vis-network-graph

Carter Hesterman · Answer 4 · Tue May 12 2020 01:02:28 GMT+0800 (China Standard Time)

As a side note, this has now been upgraded to v7:
https://github.com/hesto2/react-vis-network-graph

Patrick Jusic · Answer 5 · Sat May 23 2020 07:21:12 GMT+0800 (China Standard Time)

Thank you @hesto2, I'm using your version. I was looking for a bugfix, but it doesn't seem to fix it anyway. Maybe do you know why nodes are not redrawn after graph updates? I have a node of some color under some conditions, then the graph is updated and the node should come back to default color, but it seems redraw is not triggered, even if I explicitly call it on the network instance.

Carter Hesterman · Answer 6 · Sat May 23 2020 07:31:39 GMT+0800 (China Standard Time)

I've had a few different similar issues with edges. I think vis-network doesn't handle removing value very well. For example, if I update a node to have an opacity of 1 and then later update that node to have an opacity of undefined it will still keep the original value on there. Are you maybe running into something similar with the default color here?

…

On Fri, May 22, 2020 at 5:21 PM Patrick Jusic ***@***.***> wrote: Thank you @hesto2 <https://github.com/hesto2>, I'm using your version. I was looking for a bugfix, but it doesn't seem to fix it anyway. Maybe do you know why nodes are not redrawn after graph updates? I have a node of some color under some conditions, then the graph is updated and the node should come back to default color, but it seems redraw is not triggered, even if I explicitly call it on the network instance. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB2A4K3AR6NSYOOMHMFIO2DRS4CHHANCNFSM4J4LGJIA> .

Patrick Jusic · Answer 7 · Sat May 23 2020 09:04:43 GMT+0800 (China Standard Time)

@hesto2 yes I think we are talking about the same problem. I would expect it to work at least forcing redraw, but it doesn't seem to work. If I check nodes in network object I can see color property is no more applied to the node, but the change doesn't reflect on the ui.

Carter Hesterman · Answer 8 · Sat May 23 2020 09:35:47 GMT+0800 (China Standard Time)

Can you create an issue with your details here and I'll try and spend some time and figure it out as soon as possible: https://github.com/hesto2/react-vis-network-graph/issues

…

On Fri, May 22, 2020 at 7:04 PM Patrick Jusic ***@***.***> wrote: @hesto2 <https://github.com/hesto2> yes I think we are talking about the same problem. I would expect it to work at least forcing redraw, but it doesn't seem to work. If I check nodes in network object I can see color property is no more applied to the node, but the change doesn't reflect on the ui. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB2A4K3LSXOF6MST3RXSKYLRS4OLNANCNFSM4J4LGJIA> .

Tom · Answer 9 · Fri Nov 13 2020 16:48:10 GMT+0800 (China Standard Time)

Any ideas about version 8 ?

Vincent Lecrubier · Answer 10 · Tue Feb 16 2021 05:17:21 GMT+0800 (China Standard Time)

Done, we are now using version 9