While writing output to the xunit console I noticed that if a custom rule failed, the output to the console was doubled up. This change stores the TypeDefinition results that's returned from calling execute on the sequence and then reuses it in a failure scenario.
I've ran all the tests and it appears to look ok.
The tests have also been updated from netcore3 to net6 as it's the latest LTS version.
… once if the custom rule returns false.
While writing output to the xunit console I noticed that if a custom rule failed, the output to the console was doubled up. This change stores the TypeDefinition results that's returned from calling execute on the sequence and then reuses it in a failure scenario.
I've ran all the tests and it appears to look ok.
The tests have also been updated from netcore3 to net6 as it's the latest LTS version.