Discover module

[ProbablyClem]

Depends on this pr

Big PR that aim at being able to parse folders directly.
Currently you parse modules but using module.content only works if you have a module inside the file.

Now you can specify a directory and it will parse every files recursively.

With this new implementation, I don't need the module specification anymore because I infer it from the path, so I simplified the attributes with a new paths = "./paths1, ./path2" format which is easier to use.

The old syntax still works, I just ignore the module part.

For easier debugging, I splitted the project in 3 crates, which allows me to have most of the logic in a non-macro crate, where I can use print!(). It's way easier to debug that way !

I bumpted that projet to 4.0 because it's a big change

[rxdiscovery]

Hello,

have you thought about external dependencies? that are not on the same crate?

[ProbablyClem]

What do you mean by that ?
You mean subcrates ? Or external crates ?

[rxdiscovery]

for example, if you divide your project into several separate sub-projects, with the DTOs in one library and the controllers in another, how will you manage this?