Moshe Simantov

Looks like there is a problem in the tests.. (`next` is not a function)

If anyone needs a quick mapping from `HttpException` to gRPC: ```ts import { Catch, ExceptionFilter, HttpException, HttpStatus, } from '@nestjs/common'; import { Observable, throwError } from 'rxjs'; import { status...

I'm doing research about it a couple of hours and I think that DHT algorithm isn't fit right for WebRTC: 1. Each connection channel is only one way so each...

After some more thinking, I think that the [signaling server](https://www.webrtc-experiment.com/docs/WebRTC-Signaling-Concepts.html) is the best place for doing DHT queries. **Webtorrent** should have a few open signaling servers exactly for that case....

Thanks! It's a nice use-case and we definitely want to support it more in the future. For now, I managed to solve it by explicitly define the type and create...

I think recursive functions will break TypeScript validation and require type definition from the user, but I really like this idea! We can create `Schema.recursive` helper for that: ```ts const...

maybe `Schema.closure` is a better name then. I liked your example. Function closure is really a strong concept in JavaScript. I wonder how TypeScript will handle that.

[`either` implementation](https://github.com/neuledge/computed-types/blob/64ed3b588b25f8852f83c075bd279a0b8823a87e/src/schema/logic.ts#L151) just throws one of the errors it get from its internal items. I think it may be better to throw a custom error like "Can't find a valid...

It's impossible to detect on runtime what's the right chain methods from the object types. This is why when it's not known (like on `destruct`) it will use the main...

Looks like you need to use `Schema.either`: ```ts const Validator = Schema.either( string.min(1), Schema({ key: string }), ); ``` You can add more logic and constraints for each type individually.