Dijana Pavlovic
Dijana Pavlovic
Hello, thank you for sharing the issue with us. We'll take a look on this today.
Here is the [PR](https://github.com/edgedb/edgedb-js/pull/971) I made for fixing the first issue (cardinality of ??).
Hey @jaclarke I’m still a bit confused, the things we have in the client are methods on the client class, and then also on the server class so we call...
Form the first read I can only add: 1. what happens if user deletes` edgedb.auto.toml`, is that safe? 2. `edgedb branch rename ` if we want to rename current branch...
@scotttrinh should we finish and merge this?
Hey @manueljacob did you manage to fix this issue? I've tried to build with different node versions (with 16.18.0 too) and it worked in every case. There are many solutions...
Hey @shougan these are screenshots on smaller resolutions than desktop. I believe we don't focus too much on these now, but I'm sharing screenshots just in case. !
We fixed this issue with first @scotttrinh recommendation above. We don't return anymore "these keys" in the resulting objects.
Here are the examples of how we can use this with the Vercel SDK: [the completion route](https://github.com/edgedb/edgedb-examples/blob/add-nextjs-ai-example/nextjs-ai-new/app/api/completion/route.ts), [the chat route](https://github.com/edgedb/edgedb-examples/blob/add-nextjs-ai-example/nextjs-ai-new/app/api/chat/route.ts)
RAG provider should be fine. But I think we need to extend capabilities of the AI binding. It should support other parameters besides the query and also function calling.