Support for generic default tree structure

[aehtiopicus]

This is not an issue but i wanted to propose a runtime tree definition.

When there are lots of commands it gets harder and harder to write/maintain the file structure and in most cases it is only needed a basic tree structure like the exposed in node-cqrs example.

Is there a way to enhance the library to support a runtime tree definition?

[adrai]

not right now, but open fur the suggestion...
feel free to make a PR, so we can continue to discuss...

[aehtiopicus]

I managed to enhance the domain.js to load additional domains which are previously generated in a programmatically wey.
I am afraid that the code might not be useful but what i did Is to get the generated tree in the init function store it and then re run the first and third async block (from init) changing the domainPath and appending the new aggregators to the stored variable before
attachLookupFunctions

That it make sense???

[adrai]

And this works for you?
Should this async blocks be exposed?

[aehtiopicus]

If you want to check it it is in my fork.

[adrai]

Is it private?