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

Add externallyLoaded option to context, and load those separately #121

Merged
merged 5 commits into from
May 1, 2018
Merged

Conversation

nanov
Copy link
Contributor

@nanov nanov commented May 1, 2018

This update adds an externallyLoaded option to the context definition. Basically, this means that the user ( or more likely a library ) provides the structureLoader with an already defined context object which can be used directly ( a context object to which aggregates are added, to which commands are added and so on ).

This allows writing alternative/additional loaders, who can output the result in ready to use for this library. This will allow requests like this one and this one achieved fairly easy according to other logic/structure without breaking the existing logic/definitions.

This whole is done as are in a process of writing an on-top addition/library allowing a one-file aggregate definitions similar to other CQRS implementations.

@nanov
Copy link
Contributor Author

nanov commented May 1, 2018

Hmm, this is strnage, and has nothing to do with my changes, any ideas?

@nanov
Copy link
Contributor Author

nanov commented May 1, 2018

This seems to "solve" the problem, which apparently happens only on node 10 because it's faster :)

As i am no redis expert by any means, does those changes make sense?

@nanov
Copy link
Contributor Author

nanov commented May 1, 2018

Now i really don't get it...

@adrai any ideas?

@adrai
Copy link
Contributor

adrai commented May 1, 2018

Can you revert the redis changes (must be a node 10 problem, will look at it later)
Can you add something in the readme?

@adrai adrai merged commit f204720 into thenativeweb:master May 1, 2018
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

Successfully merging this pull request may close these issues.

2 participants