-
-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deselectNode event reports nodes, not nodeIds, in previousSelection #1688
Comments
I see this now as well. My first thought was "great, more info", but clearly this would break people's code if it was just looking for the id, and is just wholly unnecessary. Did you find the relevant code that causes this? |
Line 18179 of vis-network/esnext/esm/vis-network.js |
That path doesn't map onto what I've got, but I just submitted this pull request with a fix. You can check the actual file change as well as the code I provided in the comment which I used directly in my vis-network.min.js file. |
The documentation for the deselectNode event states that the property returned includes an array of nodeIds for the nodes previously selected:
However, using version 9.1.0, the array is not of nodeIds, but of nodes, for example:
The text was updated successfully, but these errors were encountered: