Jack Fischer

We're writing a separate file for each query.

It occurs to me that this might be query-file specific: in normal edgeql, the runtime failure is all you need, and in QB, this can be enforced. This makes me...

Certainly agree on the argument being optional for purposes like like `?? "default value" or updates. > Maybe the kind of static analysis you're looking for is whether we can...

I see (similar to the fundamental inability to know cardinality statically in [6694](https://github.com/edgedb/edgedb/issues/6694#issuecomment-1887892919)?) This situation makes sense for links, though one can enforce that say, a required UUID argument for...

Wasn't familiar with TAP but indeed that data structure sounds exactly right!

Would also make reporting minimized JS/TS related bugs easier.

+1 that the best practice is to generate the files in CI but sans that investment, our diffs are littered with meaningless noise because of the regeneration across different developer...

There is something peculiar with properties named `isActive` via QB. We get an error thrown at `toEdgeQL` on a simple select of an object including `isActive: true`. ``` [cause]: Error:...

Now seeing similar behavior with a computed boolean with a different name on a different object. So it is not the name `isActive` but perhaps something about booleans? But we've...

In our case, our next.js codebase is all typescript but VS Code running inference in the background harms productivity for pure frontend projects, where you are not dependent on knowing...