edgedb-js
edgedb-js copied to clipboard
edgedb
The official TypeScript/JS client library and query builder for EdgeDB
The majority of changes that collect over the course of our release cadence actually affect both the driver and generator. There is also a pretty tight dependency between the generator...
We do not currently generate properties for link properties in our interfaces generator. We should! Open question: Do we need a special helper type to remove these properties?
I am using [Node 16 + ESM + Strictest](https://github.com/tsconfig/bases#node-16--esm--strictest-tsconfigjson) for my tsconfig.json ```json { "$schema": "https://json.schemastore.org/tsconfig", "display": "Node 16 + ESM + Strictest", "compilerOptions": { "lib": [ "es2021" ], "module":...
Currently the `npx @edgedb/generate queries` command will generate queries for every `.edgeql` in your edgedb project (defined by the edgedb.toml), but you may not want some `.edgeql` files to be...
Similar to https://github.com/tsconfig/bases we can publish a `tsconfig.json` that has our required settings (`strict`, and `downlevelIteration`)
**Describe the bug** The `is` operator (https://www.edgedb.com/docs/stdlib/type#operator::is) is not reflected in the querybuilder. See https://discord.com/channels/841451783728529451/849374705210490900/1107383910498832397 and https://discord.com/channels/841451783728529451/849374705210490900/1060159252821463110 **Reproduction** ```typescript const person = e.select(e.Person, () => ({ filter_single: { name: "Test"...
For some consumers, the generated definition files are picked up by their editors and they are paying the price of our complex types even if they're not using TypeScript. We...
**Code** TLDR, upserts on property+link exclusivity appear broken in QB. Slack [link](https://credalai.slack.com/archives/C04BUK11UQ1/p1682978009043309) for reference The code causing the error. ```typescript e.params({ string: e.str }, (params) => e .insert(e.B, { string:...
We currently only expose a transaction that has built-in behavior with no fine-grained control over things like savepoints and rolling back.
# Request Add support for optional fields inside tuple parameters inside `e.params({ ... })` arguments. This would allow for an implicit JSON to EdgeDB mapping inside the `query.run(client, {...})` method...
