I think we should try to avoid adding new dependency.

Maybe something with dirty_equals?
Take a look at the code in the details

from dirty_equals import IsOneOf

v1 = {
    "age": {
        "title": "Age",
        "anyOf": [
            {"exclusiveMinimum": 0.0, "type": "number"},
            {"type": "string"},
        ],
    }
}

v2 = {
    "age": {
        "title": "Age",
        "anyOf": [
            {"exclusiveMinimum": 0.0, "type": "number"},
            {"type": "string", "pattern": r"^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$"},
        ],
    }
}


expected = {
    "age": {
        "title": "Age",
        "anyOf": [
            {"exclusiveMinimum": 0.0, "type": "number"},
            IsOneOf(
                {"type": "string"},
                {"type": "string", "pattern": r"^(?!^[-+.]*$)[+-]?0*\d*\.?\d*$"}
            ),
        ],
    }
}

assert v1 == expected
assert v2 == expected

I think we should try to avoid adding new dependency.

Maybe something with dirty_equals? Take a look at the code in the details

Ah yes, that works too, thanks. Amended.

I just tried running this branch with pydantic 2.12.0a1, and I have 4 failed tests

FAILED tests/test_forms_single_model.py::test_send_all_data - pydantic.warnings.UnsupportedFieldAttributeWarning: The 'alias' attribute with value 'with' was provided to the `Field()` function, which has no effect in the context it was used. 'alias' is field-spec...
FAILED tests/test_forms_single_model.py::test_defaults - pydantic.warnings.UnsupportedFieldAttributeWarning: The 'alias' attribute with value 'with' was provided to the `Field()` function, which has no effect in the context it was used. 'alias' is field-spec...
FAILED tests/test_forms_single_model.py::test_invalid_data - pydantic.warnings.UnsupportedFieldAttributeWarning: The 'alias' attribute with value 'with' was provided to the `Field()` function, which has no effect in the context it was used. 'alias' is field-spec...
FAILED tests/test_forms_single_model.py::test_no_data - pydantic.warnings.UnsupportedFieldAttributeWarning: The 'alias' attribute with value 'with' was provided to the `Field()` function, which has no effect in the context it was used. 'alias' is field-spec...

I just tried running this branch with pydantic 2.12.0a1, and I have 4 failed tests

FAILED tests/test_forms_single_model.py::test_send_all_data - pydantic.warnings.UnsupportedFieldAttributeWarning: The 'alias' attribute with value 'with' was provided to the `Field()` function, which has no effect in the context it was used. 'alias' is field-spec...
FAILED tests/test_forms_single_model.py::test_defaults - pydantic.warnings.UnsupportedFieldAttributeWarning: The 'alias' attribute with value 'with' was provided to the `Field()` function, which has no effect in the context it was used. 'alias' is field-spec...
FAILED tests/test_forms_single_model.py::test_invalid_data - pydantic.warnings.UnsupportedFieldAttributeWarning: The 'alias' attribute with value 'with' was provided to the `Field()` function, which has no effect in the context it was used. 'alias' is field-spec...
FAILED tests/test_forms_single_model.py::test_no_data - pydantic.warnings.UnsupportedFieldAttributeWarning: The 'alias' attribute with value 'with' was provided to the `Field()` function, which has no effect in the context it was used. 'alias' is field-spec...

These are due to pydantic/pydantic#12028. In that PR, @Viicos wrote:

I've reached out to the FastAPI team regarding the failing tests. They will need to address them in some way.

But I really don't follow what FastAPI is doing here; it seems to be something to do with ModelField.__post_init__ in fastapi/_compat.py? Somebody who's actually an expert in that code would need to weigh in, I think. Maybe @tiangolo?