Damian Kaczmarek

Results 192 comments of Damian Kaczmarek

@jplew I'm glad it solves your issues. Please take note of [this caveat](https://github.com/Rush/link-module-alias#if-you-use--in-your-linked-module-names-there-is-a-risk-this-module-will-cause-data-loss) but otherwise do enjoy.

It would be really useful in removing redundancy of my parser definition. I have a custom grammar that's on purpose very relaxed, and some rules need to be applied in...

> o ESM no other changes have taken place so far, it should be no problem to continue using 7.1.0 for now, I think. Not true, the dependency tree for...

I was looking through the tickets and maybe what I wrote in the past can help. I once wrote an ultra-fast snakeCase, camelize etc. conversion library https://github.com/encharm/xcase - it has...

You're probably right. The way I am trying to use `@deepkit/types` currently is more of a serialization framework than a two-way marshalling solution. And I am using `@nestjs/mongoose`. It's a...

A stretch goal would be to support some more complex cases of populate. I was able to find few of such use cases in my codebase. 1. Populate references that...

@CristianPi it could be interesting. I think if we can get DI running the rest would be easy.

From what I understand JIT (`new Function`) is instrumental to almost everything :)

This is because "compilation" actually happens at runtime.

I think one issue with RPC is that it's inherently stateful whereas REST can simply round-robin between a 100 containers, with any number of them shutting down for upgrade at...