Vicary A.

@bkniffler V3 is entering beta. I would make a stable release and move on to other features when we have solid production use cases, so you and others have a...

If TypeORM authors agree, I'd suggest simply replace all home baked recursive types with an actively maintained 3rd party package. `type-fest` is a good candidate for that.

My team has moved on to kysely, I'm unsubscribing from this issue. It's up to you guys who still cares.

@redbar0n You may be interested on this one.

@redbar0n Sorry I forgot to fork again before I start testing for nullables, the React PoC should be working now. Directives API should be easy if we have primitives sorted...

Vanilla conventions such as `.valueOf()`, `.toString()` and `Symbol.toPrimitive` would be better, it helps type coercion. I like the chaining API for directives, `$skip({ if: true })` just feels more like...

@redbar0n How would you like to add directives with *object as the API*?

Waiting for a complete toolchain before moving on towards a ESM-first repo: 1. Node 1. [ ] Build: Requires porting to a delicate esbuild setup 2. [ ] Test: Requires...

@ManfredLange Thinking Alpaca being an API-first broker, the current effort to maintain their SDK sends quite a different message TBH. Quoting [my question on discard](https://discord.com/channels/878427978223194123/951500849077698560/1314479564293931048) regarding their TypeScript SDK, ...

From my past experiences, this is usually due to an invalid schema of double arrays. For example: ```graphql type Query { foo: [[String]] # This is invalid schema definition bar:...