Bartosz Lenar

Thank you, @kislovs, for your idea. It's an interesting request and for sure I'll investigate the codebase and see how it could be done without either rewriting the big portions...

At the moment I'm pursuing for having #3 done and published in the version 2.3. It's about adding new command and while I'm coding it, I'm also investigating how much...

At the moment cutting Validot's guts open sounds like something I **don't like** to do. The core parts are polished performance-wise and marked as internal for a reason. Validot isn't...

@kislovs By the way... isn't that your case could be handled with just an extension to the specification command chain? What I mean is the extension that takes specification and...

#24 will be done, maybe even in the upcoming release 2.3. for now, you could just create two validators and move the if-ology to the upper layer. will work for...

OK, that's actually interesting. Thank you @kislovs for pointing this out, I think I will work on that soon. Few caveats, though: - I don't imagine validating keys should be...

You're right, however I think I'd proceed with placing required parameters together, so if it does use string as a key, it would be `.AsDictionary(valueSpec)` if not string, something like...

@kislovs #3 is completed as for this moment and I will be slowly drafting how `AsDictionary` could be efficiently implemented. I think this could introduce some breaking changes (so v3.0.0),...

Thank you, @kislovs, for your contribution. At first indeed it does look like it could be handled with the `AsType` and `AsChild` isn't necessary, but let me get back to...

@kislovs I'm on the #3 at the moment and it looks like this one indeed could be achieved by a special version of `AsType`. Anyway, I decided to postpone investigation...