Dealing with order in ViewModel composition

[chris-pardy]

@mauroservienti Looking at CartIdAppender it seems like it must be run before other IHandleRequests or the cart-id cookie may not exist, and operations may fail. However I don't see this being dealt with anywhere. Is there a strategy for dealing with this?

[mauroservienti]

Hi @chris-pardy. Yeah you’re right, I was in hurry with the demo and that was the first solution that came to mind. CartIdAppender doesn’t sound like the solution I was looking for, ensuring that a Cart ID is probably someone else responsibility. Not to mention that it’s a technical requirement, I’ll give it more thoughts and as soon as I come up with a better design I’ll update this issue. Thanks.

[mauroservienti]

@chris-pardy I raised #2 as a different approach to solve the problem. I haven't changed the logic, but given that now the CartId generation is completely disconnected from the ViewModel Composition process, it can be changed to whatever different requirement.

[chris-pardy]

@mauroservienti I think this approach makes sense. Giving some thought to our use case it feels like this idea works really well with CQRS so you should never have a case of needing to read data from 1 service before you dispatch a command to another service.

[mauroservienti]

Agreed. I’ll merge the PR and close this one then, feel free to reopen or raise other issues. Thanks!