use ActionCtx versions of runQuery/runMutation for compatibility#277
use ActionCtx versions of runQuery/runMutation for compatibility#277ianmacartney wants to merge 3 commits into
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
commit: |
📝 WalkthroughWalkthroughThis PR performs a systematic migration of embedding model naming across the example agent code and updates infrastructure dependencies. The core change renames Possibly related PRs
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |

In the future the
ctx.runQueryof a QueryCtx / MutationCtx may differ from ActionCtx by adding extra options (e.g. snapshot query, transaction limits). For now, the ActonCtx is the more generic version, so if the function accepts that, the user can pass any of QueryCtx/MutationCtx/ActionCtx and it should work.This is only really an issue for Workflow, where it presents as a ctx that has ActionCtx-like runQuery/runMutation/runAction, but does not have auth/storage, so doesn't match the ActionCtx here.
This change allows workflow's step (ctx) to be passed to agent functions. A follow-up (#279) could explicitly handle WorkflowCtx and pass { inline: true } for various places where it makes sense, to explicitly optimize for workflows