Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manually define aggregates #74

Open
mpseidel opened this issue Apr 14, 2016 · 4 comments
Open

Manually define aggregates #74

mpseidel opened this issue Apr 14, 2016 · 4 comments

Comments

@mpseidel
Copy link

I could not find a way to define aggregates without relying on the structureLoader mechanism.
I like the idea behind it but want to do it slightly different so that I can define multiple artifacts in the same file.

Would there be a way to provide a hook/api to define an aggregate manually somehow without rewriting too much?

I was able to define events and commands manually after init on existing aggregate definitions but for aggregates I didn't find a way.

@hilkeheremans
Copy link

Would it help if you knew you can declare your events or commands in an array in one file instead of in separate files?

@mpseidel
Copy link
Author

Didn't know that, actually :) But I'd prefer to completely opt out of the built-in structureParser instead.

@adrai
Copy link
Contributor

adrai commented Apr 14, 2016

you can try to set the tree object... https://github.com/adrai/node-cqrs-domain/blob/master/lib/domain.js#L389

@calebharris
Copy link

I would also find it useful to opt out of the directory scanning. Trying to use TypeScript for my project, but the structure parser only looks for .js and .json files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants