Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@p8 Here is a PR that changes the validations so they are all disabled by default.
I think I hit all the Readme docs as well to note that validations are optional but can be enabled either globally (via the config file) or in individual models when mounting the uploader.
Again, my argument for this is that version 0.0.15 did not have validations. So code running & tested under that version should not break due to the presence of new default validations during an upgrade. But wanted your take on it as well so I've done it on my branch first.