Niels Bantilan

I kinda don't want to re-use the term "coerce" here. `coerce=True` is already used to convert datatypes. Is there another verb we can use?

thoughts on the proposals ^^ @Smartitect @AndreaPiccione @Samreay ?

+1 to `reorder_columns=True`. On a related note, I'd love if `strict="filter"` would be deprecated in favor of `remove_extra_columns=True`

I don't believe anyone's working on this. Anyone who wants to make a PR for the `reorder_columns=True` solution has my blessing!

This looks like a duplicate of https://github.com/unionai-oss/pandera/issues/1395, correct?

Gotcha. Feel free to try and debug this and opening a PR for a fix! The part of the codebase that creates the json schema representation is [here](https://github.com/unionai-oss/pandera/blob/cf6b5e45dfb0cd593f948b12a2a327bbf3699657/pandera/api/pandas/model.py#L651-L661)

The state of the json_schema support is still the same as before, see this issue: https://github.com/unionai-oss/pandera/issues/1395 Would welcome any PRs to actually fix the to_json_schema function here: https://github.com/unionai-oss/pandera/blob/cf6b5e45dfb0cd593f948b12a2a327bbf3699657/pandera/api/pandas/model.py#L651-L661

We could support tuples as `args` in the `Field`, which wouldn't be ideal for readability, but to support semi-closed intervals, it could be something like: ```python Field(in_range=(1, 78, False, True))...

Not sure if the goal of this proposal is to make people less prone to committing errors... correct me if I'm wrong here @nathanjmcdougall but the idea is, for folks...

For folks who are encountering this: [this PR](https://github.com/unionai-oss/pandera/pull/1258) addresses the issue as a first approximation. As suggested in the PR, recursion (or another approach) would handle nested optionals, but will...