Function name should be default path name #373

Activity

1. kfirstri

   self-assigned this

   on Mar 8, 2026
2. kfirstri

   added the

   Bug

   issue type on Mar 8, 2026
3. kfirstri

   added

   enhancementNew feature or requestNew feature or request

   on Mar 8, 2026
4. github-project-automation

   moved this to Backlog in CLI Developmenton Mar 8, 2026
5. kfirstri

   added this to CLI Developmenton Mar 8, 2026
6. claude commented on Mar 8, 2026

   

   claudeBot

   on Mar 8, 2026 – with Claude

   Last edited by claude

   Contributor

   More actions

   Claude finished @kfirstri's task in 2m 35s —— View job • claude/issue-373-20260308-0922 • Create PR ➔

   ---

   Done

   • Gather context and understand the request
   • Find function schema and path-name calculation logic
   • Make name field optional in FunctionConfigSchema
   • Update readFunction to compute path-based name when name is absent
   • Add test fixture and test case
   • Run typecheck/tests (106 core tests pass)
   • Commit and push changes

   Changes made

   src/core/resources/function/schema.ts

   • FunctionConfigSchema.name changed from required to optional
   • BackendFunctionSchema now overrides name back to required, ensuring all resolved functions always have a name

   src/core/resources/function/config.ts

   • readFunction now accepts functionsDir as a second parameter
   • When config.name is absent, computes the path-based name using relative(functionsDir, functionDir) — identical to how zero-config functions are named

   tests/

   • Added tests/fixtures/function-discovery/no-name-in-config/function.jsonc (no name field) + entry.ts
   • Added a test verifying the path-based name fallback works for config-based functions without a name
   • Updated expected function count from 4 → 5
7. claude

   added a commit that references this issue on Mar 8, 2026

   Make function name optional in function.json schema, fall back to pat…

   ...

   This issue will close once commit 0a641f5 is merged into the 'main' branch.

   0a641f5
8. kfirstri

   moved this from Backlog to In progress in CLI Developmenton Mar 8, 2026