Repository navigation
Planned bindings missing for non-error methods (Exists, IsDir, IsFile, Name, Parent, Join) #171
Description
TestPlannedBindings fails with plan.file has no .exists attribute.
RegisterReflectedActions skips methods that don't return error as the last value. This means Exists, IsDir, IsFile, Name, Parent, and Join are not registered as actions. Since the planned layer references action names to create graph nodes, these methods are unavailable as planned bindings.
The old hand-coded planned receiver exposed all methods (including non-error ones) as graph node creators. The reflection-based action layer needs a mechanism to register non-error methods as actions, or the planned layer needs an alternative path for these methods.
Branch: feature/binding-unification
Activity
feature(e2e): devlore-test binary + graph test harness — Phase 0
feature(op): ResourceManager, NamespaceMap, and URI helpers — Phase 1 (…
feature(op): Resource management — Phases 0-2 (#177)
feature(op): Resource management — Phases 9-11, epic complete
feature(op): Resource management — Phases 9-11, epic complete (#187)
David-Noble-at-work commentedon Mar 11, 2026
Resolved. Exists, IsDir, IsFile now return (bool, error) and are registered as reflectedFallibleAction. Name, Parent, Join return without error and are registered as reflectedPureAction. All six are exposed in the planned layer.