-
Notifications
You must be signed in to change notification settings - Fork 78
Replace pygraphviz with neo4j-viz for graph visualization #306
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
base: main
Are you sure you want to change the base?
Replace pygraphviz with neo4j-viz for graph visualization #306
Conversation
1cb21f1
to
0a14de3
Compare
This commit replaces pygraphviz with neo4j-viz for pipeline visualization, providing a more interactive HTML-based visualization experience. The changes include: - Updated the Pipeline.draw() method to generate HTML output using neo4j-viz - Added a new get_neo4j_viz_graph() method while maintaining backward compatibility - Updated dependencies in pyproject.toml to use neo4j-viz instead of pygraphviz - Updated documentation and examples to reflect the change from PNG to HTML output - Updated unit tests to work with the new visualization implementation - Added stub file for neo4j-viz to make mypy happy
2916e37
to
54fe2eb
Compare
relationships.append(rel) | ||
|
||
# Cast the constructor to Any, then cast the result back to VisualizationGraph | ||
viz_graph = cast(Any, VisualizationGraph)( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the mypy error without this cast?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, isn't the pyi
file supposed to help mypy here? Otherwise why do we have this file?
Just realized we can remove pygraphviz install from the GH actions ( |
Neo4j has its own viz library, let's use that!
Type of Change
How Has This Been Tested?
Checklist
The following requirements should have been met (depending on the changes in the branch):