You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why no replacement to Package from CHAP links.Network ?
I upgraded my project to vis.js but there is no feature to illustrate communication between the nodes. Was there any specific reason to not keep Package from CHAP ?
I'm planning to implement a replacement for it for myself locally, do you have any advice or warning on how to do it ? (especially if answer to 1) is "Yes)
Would it be relevant to integrate such a feature into vis.js ?
The text was updated successfully, but these errors were encountered:
No general advice now, other than please do send a PR when you have the replacement working! If it is useful to you, then I imagine that it is also useful to others in the community 😄
I think so. I tend to take a liberal view on contributions, welcoming most new features here.
Thank you for your answer @micahstubbs.
It probably does date back a lot. I guess I have to try and see for myself if there is any incompatibility.
I'll be sure to submit a pull request when I achieve a satisfying result.
In the mean time, if anyone else has anything to say about such a feature and its implementation, they're very welcome 🤗
micahstubbs
changed the title
Why no replacement to Package from CHAP links.Network ?
add functionality from CHAP links.Network package
Jul 19, 2019
I've edited the title of this issue, and will keep it open as a feature request, in case you or another community member wants to add this functionality.
Why no replacement to Package from CHAP links.Network ?
I upgraded my project to vis.js but there is no feature to illustrate communication between the nodes. Was there any specific reason to not keep Package from CHAP ?
I'm planning to implement a replacement for it for myself locally, do you have any advice or warning on how to do it ? (especially if answer to 1) is "Yes)
Would it be relevant to integrate such a feature into vis.js ?
The text was updated successfully, but these errors were encountered: