Graphify files are taking absolute path instead of relative path

[kenn850]

When I created a graph for my project, it created json file and html file which has absolute path (E.g. "C:\myproject\src...") instead of relative path (E.g. "\myproject\src...")

This restricts the portability and I my team is not able to use the graph from my commit.

[elbruno]

🎉 Issue Fixed and Merged

This issue has been resolved by squad and merged into main (commit c22c426).

What was fixed:

• Graphify now exports JSON and HTML files with relative paths instead of absolute paths
• Example: src/Class1.cs instead of C:\myproject\src\Class1.cs
• Paths are normalized to forward slashes for cross-platform compatibility
• Exported graphs are now portable across teams and machines

Implementation details:

• Extended extraction and graph models to track relative paths throughout the pipeline
• Exporters (JSON and HTML) now serialize relative paths with fallback to absolute paths for backward compatibility
• All 614 tests pass (573 unit + 41 integration)

Thank you @kenn850 for reporting this issue! Your team can now share graph files across commits and machines. 🚀

[kenn850]

Thanks for the update. But I don't see the new release version here yet.

Please let me know when this will be released.

Thanks @elbruno

[elbruno]

@kenn850 ... I miss that! Publishing the v0.6.1 now!

[elbruno]

🎉 Release Published: v0.6.1

The fix for this issue has been released to NuGet as v0.6.1.

What's included:

✅ Graph exports now use relative paths instead of absolute paths
✅ Paths normalized to forward slashes for cross-platform compatibility
✅ Backward compatible with existing graphs
✅ All 614 tests passing (573 unit + 41 integration)

Install the latest version:

\\�ash
dotnet tool install -g graphify-dotnet --version 0.6.1
\\

Or upgrade:
\\�ash
dotnet tool update -g graphify-dotnet
\\

Release Details:

🔗 Release v0.6.1
📦 NuGet Package

Thank you @kenn850 for reporting this issue! Your team can now share graph files across machines and commits. 🚀

[elbruno]

✅ Resolution: The absolute path issue has been fixed and published!

📦 Version: v0.6.1 is now available on NuGet

Installation:
\\�ash
dotnet tool install -g graphify-dotnet --version 0.6.1
\\

What's Fixed:

• Relative paths are now properly used in JSON and HTML exports
• File paths in graph exports are now portable across different machines and directories
• The exporter preserves relative path information from the extracted graph nodes

Try It Out:
Simply update to v0.6.1 and your graphs will now use relative paths instead of absolute paths, making them portable and shareable with your team.

Thank you for reporting this issue!

[kenn850]

@elbruno

This issue still persists in the version 0.6.1. I have tried builing the graph and it still stores absolute path in the json file.

Another thing I noticed is that when I tried to generate Graph: 10881 nodes, 17927 edges, it took hours to build one.
I have a solution for these issues, I can raise a pull request with the code changes if access is given for the same.

Thanks

[kenn850]

My bad @elbruno

Path issue is fine now. But the Step 2 and 4 is too slow (especially 4).
I have found the solution to it

The code in the main took more than 24 hours to build a Graph: 47026 nodes, 76987 edges.
My change made it under 5 minutes which more than 150x faster