Samuel Colvin

"Plus one" me if you want full strictness; effectively `isinstance(input_value, field_type)` - close to the type checks on statically typed language.

"Plus one" me if you want partial strictness; * coerce from JSON types to more "complex" python types, e.g. `string` to `UUID` * but validation errors if you pass the...

If sounds like you want the partial strictness I suggested above. `parse_raw` is just decoding followed by `parse_obj`, I don't what that to change and do more complex things like...

> Are you interested in having this feature in Pydantic Yes I want the functionality that I think you're looking for. Hence why I'm spending time on this issue, if...

Makes sense to me. @tiangolo what do think?

We won't make any changes to JSON Schema in v1.10 now. On V2, we're targeting JSON Schema 2020-12. No idea how this maps to `$schema`, I'll need to dig further....

Agreed, also easier to see and remove/change it than remember to add it. Therefore #5029 will close this.

For now it'll always be 2020-12, if someone wants to try and write a wrapper that infers the oldest compatible draft, happy to review a PR. But honestly, that sounds...

That's fine for them, but their schemas are mostly hand written, so that recommendation is reasonable actionable.

No, I want the scheme for that URL, which is exactly what OPTIONS requests are for.