Split validation into two distinct paths

[wendelfabianchinsamy]

Purpose

closes: datacite/datacite#2142

Approach

Open Questions and Pre-Merge TODOs

Learning

Types of changes

• Bug fix (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 change)

Reviewer, please remember our guidelines:

• Be humble in the language and feedback you give, ask don't tell.
• Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
• Offer suggestions on how to improve code e.g. simplification or expanding clarity.
• Ensure you give reasons for the changes you are proposing.

[richardhallett]

I'm curious, did your editor make these space/tab changes through the files? Or was it the result of go fmt? Because if it's the former then it should be the latter.

[wendelfabianchinsamy]

@richardhallett it was done by the standard go tooling. i noticed that it was formatting the files i worked on, on save (this is how i've set up my editor). so i ran go fmt ./... on the project to format it such that it adheres to the go standards.