Attila Oláh

> github docs also is not a good place for docs Github will generate a website from it, you dont have to read it on the repo, so the docs...

> I don't like coding html when we have markdown and build engine for generating docs site. Yes I vote also to use some already built solution, Gitbook or the...

Also a think we havent discussed about, we should create a code style, and add some tooling for it. For example my editor is configured totally differently by default, so...

> No, no, no! For God's sake! 😖 That's why: I can say the same, using 4 spaces nest the code way too fast, forcing you to split your code...

> I don't think I will agree on changing 4 spaces to 2 here and in other projects. Then it's decided I guess, hehe. > For coding style we can...

> Website - along with docs, I think there needs to be a landing page for this project with a very simple and impressive block of "Getting Started" code that...

@AnimaMundi thanks for weighting and for the clarification! > This is something I planned from the beginning - use express/koa/something else community wants and later write its own router/engine/framework once...

Koa support is being dropped.

Hi! This is the expected behavior. Since TypeDI 0.9.0 it won't create instances for unknown classes, so you need to decorate your classes. This needs to be documented and also...

Let's keep this open for tracking. I think we may auto-register services, but we need to discuss this further.