function as parameter omitted in 2.2.0

[doctorgu]

get_db_read function is actually calling but disappeared in 2.2.0

• sample.py

from fastapi import Depends
from database.depends import get_db_read

def get_id(db = Depends(get_db_read)):
    return db.query(1).all()

• test code for sample.py

def bug_depends_get_db_read():
    """
    bug depends get_db_read
    """
    
    file_name = os.path.join(os.path.dirname(__file__), "sample.py")
    visitor = CallGraphVisitor([file_name])
    visitor.process_one(file_name)

    # traverse all children deep
    edges = visitor.uses_edges
    for start_node in edges:
        descendants = set()
        stack = [start_node]
        
        while stack:
            curr = stack.pop()
            for child in edges.get(curr, set()):
                if child not in descendants:
                    descendants.add(child)
                    stack.append(child)
                    
        for child in descendants:
            print(f"{start_node.namespace}.{start_node.name} -> {child.namespace}.{child.name}")

• 2.1.0:

.sample -> database.depends.get_db_read
.sample -> fastapi.Depends
sample.get_id -> database.depends.get_db_read -> disappeared
sample.get_id -> fastapi.Depends
sample.get_id -> fastapi.Depends.query

• 2.2.0:

.sample -> database.depends.get_db_read
.sample -> fastapi.Depends
sample.get_id -> fastapi.Depends.query

[Technologicat]

Fixed in df85eb2.

Root cause: The 2.2.0 fix for #61 (lambda as default argument crash) moved default-value visiting from inside the function scope to the enclosing scope, which is correct per Python's evaluation semantics and necessary for symtable consistency. However, as a side effect, uses edges were now attributed to the enclosing scope (the module) instead of the function — so sample.get_id → get_db_read and sample.get_id → Depends were lost (only .sample → ... remained).

Fix: After entering the function scope, a new method _record_default_uses_in_function walks the default-value ASTs and adds supplementary uses edges from the function to each referenced name. This restores the function-level edges without re-triggering the full visitor machinery (which would conflict with symtable scope expectations).

Thanks for the clear repro — it made this straightforward to diagnose.

— Claude (Opus 4.6)

[Technologicat]

Also, on my part - thanks for the clear example, it made this easy to diagnose. A unit test case has been added to make sure this doesn't break again.

Thanks for reporting the issue, and enjoy the fixed version. The fix will be included in 2.3.0 - in the meantime, it's available on the master branch.

—Technologicat

[Technologicat]

Decided to release this as a hotfix, version 2.2.1. Now available on PyPI.

—Technologicat