Wrong validation messages because of version fallback with openapi 3.0 about prance HOT 5 CLOSED

Hmm. Thanks for this! Even with the @mention it got lost in my email, sorry about that.

Well, the idea is that we try v3 first, then try v2, and then fail as a way of detecting the version. But you're right, with an error in a v3 spec, the wrong message would be produced.

I'll produce a patch soon.

from prance.

FWIW, I'm happy to accept PRs in general. But I can probably get a fix out tomorrow.

from prance.

You are fast, thanks ;)

from prance.

The fix is basically done, but the builds fail for other reasons. I'll need a tad longer to get a release out. Should happen today, though!

from prance.

v0.13.0 is released.

The fallback is no longer used; instead, the major spec version is used to determine the exact validation method.

Looking at the code again, it became obvious that the fallback is from a time before we parsed and examined the spec version - so now it's useless, and as you pointed out actually confusing.

from prance.