The verification UI flow in mirror-node explorer needs to be able to call the/session/verify-checked API end-point without actually persisting the result of the verification in the repository.
This is required in order to be able to obtain an exact preview of what the result of the verification is going to be for a given contract.
Solution
Add an optional dryRun argument (or a query parameter) to the/session/verify-checked end-point
when set to true, the verification result should not be stored in the repository
when set to false, the result should be stored in the repository
when undefined, the value false should be assumed, to be compatible with the current API behaviour
Problem
The verification UI flow in mirror-node explorer needs to be able to call the
/session/verify-checkedAPI end-point without actually persisting the result of the verification in the repository. This is required in order to be able to obtain an exact preview of what the result of the verification is going to be for a given contract.Solution
Add an optional
dryRunargument (or a query parameter) to the/session/verify-checkedend-pointtrue, the verification result should not be stored in the repositoryfalse, the result should be stored in the repositoryundefined, the value false should be assumed, to be compatible with the current API behaviourAlternatives
No response