not sure if that's something that really needs to be added to the docs

Hi, @nicolas-grekas , this isn't complete. I think it would be fine if followed by one more PR

Please send the PR if you want to rediscuss of course. I engaged in the discussion but other people or arguments might shed another light.

Hello @nicolas-grekas !

I want to rise again the topic of valued exceptions.

The primary use case of this would be that the value will appear in logs, ready for the analysis.

For example, condiser the application where we'd receive messages from a separate system and then process them. External system might not enforce the invariants they say to enforce, and it happens that they publish values that are not uuid, although they thought them to be so. In this case we'd like to know what actual invalid uuids they have provided. If we use fromBase32 or some other Uuid factory methods providing no context, we would not find the value.

I propose to add the value to the exception, so that after being serialized by the log processor, the value will finally appear in logs. Thus exception context could easily appear in logs as dedicated fields, which can be filtered by, and grouped by.

Please send a PR to the Symfony code repository with the changes that you in mind to gather feedback on your idea.