PydanticSerializationError missing validation error field name

[ddennerline3]

I am getting quite a few of these Expected 'int' but got 'float' - serialized value may not be as expected warnings in the log files. Is there a way to callout the specific field name?

I looked at Rust's exception and error message, and I don't see any "add_variable_context" flag.

If not easily possible, would it be possible to add the field name that is triggering the warning to PydanticSerializationError please.

The object that is triggering the exception has large number of sub-objects and fields, so going through all the fields would be very time consuming.

# Internal imports

# External imports
from pydantic import BaseModel
from pydantic_core import PydanticSerializationError


# Own imports

class TestModelDump(BaseModel):
    int_value: int | None = None
    float_value: float | None = None


def test_mismatch():
    valu = TestModelDump(int_value=1, float_value=1.0)
    result = valu.model_dump_json()
    print(result)

    valu = TestModelDump(int_value=1.0, float_value=1.0)
    result = valu.model_dump_json(warnings="error")
    print(result)

    valu = TestModelDump(int_value=1.0, float_value=1)
    valu.int_value = 1.0
    valu.float_value = 1
    try:
        result = valu.model_dump_json(warnings="error")
    except PydanticSerializationError as e:
        print(e)
    else:
        print(result)

[davidhewitt]

Seems like a reasonable request to me, I think this just needs some refactoring. cc @sydney-runkle

[sydney-runkle]

Indeed, a good first issue if anyone wants to pick this up.

[joabreu]

I can pick this one up and contribute, can you please assign me along with @crdsteixeira? We can pair.

Thanks,
Jose

[crdsteixeira]

I'm up for it 😃

[crdsteixeira]

Hi @sydney-runkle , can you please assign us the issue? 😊

[wevonosky]

Hey @joabreu / @crdsteixeira just checking in to see if you are still working on this? I am new to Rust and looking for a way to contribute while learning so just bouncing around looking for issues that seem doable. Also would be psyched to peer code something like this. Let me know!

[crdsteixeira]

Hi @wevonosky, yes we are still working on this ☺️

[Stormageddon37]

Is this still a WIP? If not, I'd love to give this a go.

I did notice that #1377 (sort of) seems to address this issue but solves in another way so is this still relevant?

[Viicos]

#1799 Adds the field name as a start to giving better location context. Next steps tracked in pydantic/pydantic#10495.