Scott Trinh

@Arrow7000 Working on putting together a release today, so I'd say in the next 24 hours!

@dotlouis FWIW, we do have something _close_ to this in the form of `e.all` which would look like: ```ts e.all(e.set([e.op(), e.op(), e.op()])); ``` Which uses the [`all` standard library function](https://www.edgedb.com/docs/stdlib/set#function::std::all)...

@dotlouis There is some existing guidance in the "Filtering" section of the client docs here: https://www.edgedb.com/docs/clients/js/select#filtering Also, there is some similarity here between TypeScript/JavaScript's `&&`/`||` operators and the `Array.prototype#every`/`Array.prototype#some`, so...

@samwinslow @haikyuu Having whitespace in the path is fixed on `master` as of #582

btw, inferring the cardinality based on the filter was removed in https://github.com/edgedb/edgedb-js/pull/460 ostensibly due to TypeScript recursion depth issues on the type that inferred the cardinality from the filter itself....

Going to close this specific issue in favor of discussion within #340 . Feel free to subscribe and/or comment there.

While some details have changed, and some tools like `@edgedb/migrate` have not materialized yet, I'm going to close this as completed due to the majority of the organizational changes that...

Implemented in the query builder: https://www.edgedb.com/docs/clients/js/querybuilder#select-a-single-object

This appears to be fixed in the latest version and has test coverage.

Is this still desirable given the `queries` generator gives us something pretty close to this experience without needing to jump through a bunch of tooling hoops to get good type...