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

Elixir: defdelegate function definitions are dropped

Open
  • Is something wrong?
#4,132 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #4133 by @rajatnagda45 — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
elixir, python
Domain
devtools

Research direction

Start with extract_elixir and the def-handling keyword set mentioned in the issue. Run the supplied facade.ex reproduction and inspect the extracted nodes and calls. Done means start and stop appear as function nodes and run has calls to both; a linked pull request is already open.

Written by the indexing model from the issue text.

Description

Version / commit

v0.9.77 (v8 @ 5c7b847)

Environment

macOS, Python 3.13, clean checkout of v8.

What happens

defdelegate name(args), to: Mod defines a real, public module function (it forwards its body to another module), but it is not extracted. The delegated function never becomes a node, and an intra-module call to it resolves to nothing — so parts of a module's public surface vanish from the graph.

Minimal reproduction
# facade.ex
defmodule Facade do
  defdelegate start(x), to: Worker
  defdelegate stop(x), to: Worker, as: :halt

  def run(x) do
    start(x)
    stop(x)
  end
end

from graphify.extract import extract_elixir
r = extract_elixir("facade.ex")
print(sorted((n.get("label") or "").rstrip("()") for n in r["nodes"]))
# -> ['Facade', 'facade.ex', 'run']   # start / stop missing
print([(e["source"], e["target"]) for e in r["edges"] if e["relation"] == "calls"])
# -> []   # run -> start, run -> stop unresolved
Expected vs actual
  • Expected: start and stop function nodes, with run --calls--> start and run --calls--> stop.
  • Actual: the delegated functions are absent and the calls dangle.
Root cause

defdelegate has the same call head shape as def (its first argument is the function signature), but it is not in the def-handling keyword set, so it falls through to the generic recursion and is dropped.

A clean checkout of v8 reproduces it. Fix PR to follow.

Dominant language
Python
Stars
124k
Forks
11.9k
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 Graphify-Labs/graphify

All issues in Graphify-Labs/graphify

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.