Alessandro Lai

IMHO this should be handled using custom class serializers, which is documented in the readme: https://github.com/getsentry/sentry-symfony#custom-serializers Adding an interface that has `getId` to intended classes should make the trick.

> The ODM and ORM 2.x use an array and ORM 3.x uses an object that implements `ArrayAccess` and triggers deprecations when using array access. I'm probably missing something here,...

I did a first attempt to solving this, at least partially, with #2889

Blocked by https://github.com/psalm/psalm-plugin-phpunit/issues/154

Surely, it would make sense to have spaces, since [4.7 says](https://github.com/php-fig/per-coding-style/blob/master/spec.md#47-method-and-function-calls): > In the argument list, there MUST NOT be a space before each comma, and there MUST be one...

@keradus as you can see, my CI is green even under PHP 8.5: https://github.com/facile-it/paraunit/actions/runs/16993356550/job/48177975461?pr=327 So, I cannot reproduce any issue here, and I do not see any issue specific of...

Thanks to #328 it's now failing due to some deprecation inside Composer's vendor folder: ``` PHP Deprecated: Case statements followed by a semicolon (;) are deprecated, use a colon (:)...

Couldn't you fix this programmatically, by passing the current dir to Sentry when initializing it? Sentry-symfony does this by getting the `project_dir` parameter from the framework.

Agree on this, but it may need to be considered a breaking change. I do this in my projects with this configuration: ```yaml sentry: options: ignore_exceptions: - Symfony\Component\Security\Core\Exception\AccessDeniedException - Symfony\Component\HttpKernel\Exception\NotFoundHttpException...

Ouch sorry my bad, I mistook this for default config for errors, not traces. In any case, those exceptions are how Symfony reports 404 and 403, so it's still what...