Skip to content

fix: clarify functionRootPath source directory contract#569

Open
binggg wants to merge 1 commit intomainfrom
feature/attribution-functionrootpath-standard-dir
Open

fix: clarify functionRootPath source directory contract#569
binggg wants to merge 1 commit intomainfrom
feature/attribution-functionrootpath-standard-dir

Conversation

@binggg
Copy link
Copy Markdown
Member

@binggg binggg commented Apr 18, 2026

Summary

  • clarify manageFunctions.functionRootPath as the direct cloud function source directory instead of a generic project root
  • strengthen HTTP path error guidance so the model is told to pass cloudfunctions / functions, not the project root
  • refresh generated tool docs and add regression checks for the stronger wording

Attribution

Verification

  • cd mcp && npx vitest run src/tools/functions.test.ts
  • node --input-type=module -e ... listTools() runtime schema check confirmed functionRootPath description now includes project-root warning
  • evaluation: atomic-js-none-cloudbase-hello-function/2026-04-18T01-01-19-60f057 -> pass (5/5)

@chatgpt-codex-connector
Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify manageFunctions functionRootPath should target cloudfunctions/functions dir, not project root

1 participant