🐛 Keep an explicitly assigned empty namespace at collection

[elinscott]

Problem

from typing import Annotated

from node_graph import namespace, task


@task.graph()
def my_graph(data: Annotated[dict, namespace(x=int)]) -> dict:
    return {}


my_graph.build(data={})
# TypeError: my_graph() missing 1 required positional argument: 'data'

The error is wrong: the caller passed data explicitly; the error says they didn't.

The mechanism: TaskSocketNamespace._collect_values kept a child namespace only if its collected dict was truthy, so an assigned-but-empty namespace was indistinguishable from a never-assigned one by the time the graph body was called.

Changes

• A namespace remembers that a dict was assigned to it (_explicitly_assigned, set by _set_socket_value), and _collect_values keeps it even when it collects to nothing — the body now receives {}.

Testing

• The example above builds; a populated namespace still collects its members (control in the same test).
• Reverting the _collect_values change fails exactly the new test; the full suite passes (310) with it in place.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.70%. Comparing base (8d85e61) to head (adc405f).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #170      +/-   ##
==========================================
+ Coverage   89.68%   89.70%   +0.02%     
==========================================
  Files          81       81              
  Lines        8984     8996      +12     
==========================================
+ Hits         8057     8070      +13     
+ Misses        927      926       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.