What's your strategy to provide a dry-run capabili...
# arrow
c
What's your strategy to provide a dry-run capability to your domain methods? e.g. the UI should be able to dry-run an action to know what pre-requisites are not valid yet, but without actually running it because the user may not have validated it.
I'm thinking of having an "Event" class that contains the validation, and the actual operation takes an instance of that class and makes the change, with guarantees that the validation has already been performed. But then that I have to hide the constructor somehow to be able to use context parameters for the construction…