Why disabling validation feature was removed?

[rastuhacode]

First of all thank you for this library and your work!

I have a schema which isn't fully valid but all errors are not critical. If I manually patch orval to log warnings instead of throwing Errors after failed validation it generates the valid types.
While it's true that the focus should be on fixing the spec itself I'm still curious why validation option was removed in #2614 for temporary disabling validation for migration / edge cases?
Is there some reason / technical restrictions why this option was removed?

[melloware]

@snebjorn ??

[snebjorn]

@rastuhacode the reasoning was that we cannot build an accurate model of what's in the spec if it contains errors.

Forcing a valid spec was the easy solution as we wouldn't see bug reports about erroneous code generation when the problem was the spec.