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
Hi. I found that 'JohnKomov' and 'JohnKomov\n' are the different names for merging code and the same ones for Gephi itself. The result of such duality is a Java Exception and two nodes with the same visible names and different sets of edges. Check out other non-alphabetical symbols too (I didn't check).
The text was updated successfully, but these errors were encountered:
I'm sorry but that is a input issue. We don't want to introduce rules such as cleaning '\n' from input ids or labels as it could introduce confusion. However, it could be added as a "Warning" for instance in the import report.
mbastian
changed the title
An unpleasant posibility with nodes' names
Add warning when element IDs match without special characters such as new lines
Apr 16, 2016
…lements id (#2644)
* Check newline characters, leading and trailing space.
* Refactored checkSpecialCharacter function
* Added unit test
* Fix test and improve function
* Variable name
Co-authored-by: Walton Goga
Hi. I found that 'JohnKomov' and 'JohnKomov\n' are the different names for merging code and the same ones for Gephi itself. The result of such duality is a Java Exception and two nodes with the same visible names and different sets of edges. Check out other non-alphabetical symbols too (I didn't check).
The text was updated successfully, but these errors were encountered: