List.traverseValidationA and List.sequenceValidationA now preserve the order of errors

[ursenzler]

Proposed Changes

Preserve the order of errors when executing List.traverseValidationA - and as a consequence for List.sequenceValidationA.
Fixes Should List.sequenceValidationA preserve order? #191

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Could however be a breaking change because it changes the behaviour!

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Build and tests pass locally
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Further comments

I think this is rather straight forward :-)

Let me know if something needs to be changed. E.g. I didn't format it with Fantomas because other parts of the file would have been changed as well.

[TheAngryByrd]

Minor Change but looks good otherwise.

[TheAngryByrd]

I didn't format it with Fantomas because other parts of the file would have been changed as well.

That's fine. Go ahead and format it. I'm used to it by now.

[ursenzler]

I formatted List.fs with Fantomas, but it's not in an accepted format. I'm a bit lost here.

[TheAngryByrd]

hmm did you run build.cmd/sh formatcode or did you run it from your editor? I don't know if VS or Rider pickup the dotnet tool correctly, which the FAKE build is using the dotnet-tool.

[ursenzler]

ah, I see. I ran it from the editor.

[TheAngryByrd]

Thank you!

[ursenzler]

Thanks for this excellent library!!