Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Edge routing

Open
  • Is something wrong?
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
computer-graphics

Research direction

The issue names no files, tests, or entry points; start by inspecting the repository's existing layout implementation and the referenced edge-routing material. Define the polyline-routing baseline first, including node-boundary clipping, and treat spline fitting as a later enhancement; done should be demonstrated by routed paths that follow hierarchical virtual-node positions.

Written by the indexing model from the issue text.

Description

enhancement

After layout assigns node positions, edges need to be routed as concrete paths between nodes. This involves three layers of increasing sophistication.

Node boundary clipping computes where an edge line intersects the source and target node shapes, so edges terminate at shape boundaries rather than node centers. This requires intersection functions for each shape type (ellipse, rectangle, polygon). Polyline routing threads edges through the positions of virtual nodes inserted during hierarchical layout, producing multi-segment paths that follow the layered structure. Spline fitting converts polyline control points into smooth cubic Bezier curves. The `splines` graph attribute controls which mode is used. Polyline routing should be implemented first as the baseline, with spline fitting as a follow-up enhancement.

References

Dominant language
Rust
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from terror/dotgraph

All issues in terror/dotgraph

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.