Closed AlexandreRoba closed 8 years ago
Hello,
After a little more investigation I find out that setting the priority did resolve the issue. Isn't this suppose to be optional? Nevertheless it now works with the priority set.
thanks,
Alex.
Yes the priority is optional (defaults to Infinity), it should work without priority too.
Hello, @adrai!
I just also encountered with this issue by its nature, and, as there OP pointed cause of this by setting priority, for me does not solve this solution.
I have made own investigation by debugging to figure out how it actually handles pre-load conditions of command. and I have cause of this. The problem is place where it checks for defined pre-load conditions by checking it's length of pre-load conditions array in particular command instance. Acually it looks in preConditions
array instead of preLoadConditions
which means it apply pre-load conditions only if pre conditions is present in command.
You're right... will fix asap
v2.4.8
Hello,
I have a domain with one aggregate and two commands. I have defined two preload conditions for each commands. I can see on the getInfo for each commands both preload conditions. When I submit the command matching the preload condition commands, none of the preload function are called. I have added logging and breakpoints. None of them are called or stopped at. the preload condition are qui simple. I'm for exemple checking for a meta with a userId:
Any idea?
thanks for your help,
Alex