Closed gabriella-bankova closed 7 years ago
Is this change really solving your issue? Can you provide a test?
Yes, it does solve an issue for commands that have no aggregate or context specified. After applying this, it correctly finds the aggregate revision number from the store:
Before it would always set it to '1':
I saw that you had considered adding this before directly in the var streamInfo and it seems to be the only was to resolve my problem.
Well, otherwise you have to explicitly specify aggregate name in each command you dispatch. In a scenario in which you want the revision number from the stream info and not from the command it is extremely helpful.
Set aggregate and context names correctly in var streamInfo when they are not defined in command. Otherwise may not resolve revision number correctly.