Michael Bleigh
Michael Bleigh
Since we have to read the email out of the `USERS_COLLECTION` anyway, it seems pretty reasonable to be able to access other fields in that document via something like `{{user.field_name}}`....
Why do this? Most guidance I've seen is to put this in deps, not devDeps. I think there's too much risk for no enumerated benefit On Sun, Apr 6, 2025,...
In addition to streaming tool requests, I would like to see streaming resource updates (if you subscribe to updates for a resource, the notification can send additional payload information about...
A simple solution to this could be to add a notification type for this: ```js { "jsonrpc": "2.0", "method": "notifications/tools/progress", "params": { "name": "name_of_tool", "id": 123, // request id of...
Is this supposed to be targeting `next` instead of `main`? I'm seeing a ton of unrelated changes.
+1 to both getting rid of candidates generally and still supporting multiple generations for image models specifically. :)
@gspencergoog I know it's been forever on this -- we're in the middle of revamping the MCP plugin with a pretty big rewrite and this got caught in the middle....
I'll close it out - #3074 adds roots to the new implementation 😄 but thank you!
Big 👍 to this issue. In our case we we have generic resolvers and want to be able to declaratively map application-specific input types (e.g. values of a form) to...
I think the two core issues problems with the existing syntax that I can't address easily are: 1. Namespacing 2. Reusability In a simple example like the above I'd agree...