If the TraceableSerializer runs from a callable in an array_map, then
the caller looses the file and the line because it was invoked. This
causes a hard fail since the required items are not defined. The error
is the following:
TraceableSerializer.php line 174:
Warning: Undefined array key "file".

The fix is to get the file and the line from the following array item
which always is the caller class.

Fixes #60214

Currently it's not possible to serialize an object using the PropertyNormalizer when a
DiscriminatorMap attribute is used.

It produces the following error:

> Symfony\Component\Serializer\Exception\NotNormalizableValueException: Type property "type" not found
> for the abstract object "Symfony\Component\Serializer\Tests\Fixtures\DummyMessageInterface".

The ObjectNormalizer overrides the `getAllowedAttributes` from AbstractNormalizer and adds support for
discriminators. But the PropertyNormalizer does not do this. Therefore it doesn't work.

For now, we copy the logic from ObjectNormalizer to PropertyNormalizer and the problem goes away.

…callable inside `array_map` (OrestisZag)

This PR was merged into the 6.4 branch.

Discussion
----------

[Serializer] Fix `TraceableSerializer` when called from a callable inside `array_map`

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        |
| License       | MIT

If the `TraceableSerializer` runs from a callable in an `array_map`, then the caller looses the file and the line because it was invoked. This causes a hard fail since the required items are not defined. The error is the following:
```
TraceableSerializer.php line 174:
Warning: Undefined array key "file".
```
The fix is to get the file and the line from the following array item which always is the caller class.

Commits
-------

490a110 Fix TraceableSerializer when collected caller from array map

* 6.4:
  [Validator] Remove comment to GitHub issue
  [Serializer] Add support for discriminator map in property normalizer
  [DependencyInjection] Fix inlining when public services are involved
  fix contracts directory name
  Fix TraceableSerializer when collected caller from array map
  [HttpClient] Limit curl's connection cache size
  [FrameworkBundle] Fix argument not provided to `add_bus_name_stamp_middleware`

* 7.2:
  [Validator] Remove comment to GitHub issue
  [Serializer] Add support for discriminator map in property normalizer
  [DependencyInjection] Fix inlining when public services are involved
  fix contracts directory name
  Fix TraceableSerializer when collected caller from array map
  [HttpClient] Limit curl's connection cache size
  [FrameworkBundle] Fix argument not provided to `add_bus_name_stamp_middleware`

This PR was squashed before being merged into the 7.2 branch.

Discussion
----------

[TypeInfo] Fix handling `ConstFetchNode`

| Q             | A
| ------------- | ---
| Branch?       | 7.2
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | Fix #...
| License       | MIT

I cannot upgrade to 7.3 because I get:

```
  In StringTypeResolver.php line 88:
!!
!!    Cannot resolve "array{requirement: ProductLicense::SYSTEM_REQUIREMENT_*, va
!!    lue: non-empty-string}".
!!
!!
!!  In StringTypeResolver.php line 142:
!!
!!    Unhandled "PHPStan\PhpDocParser\Ast\ConstExpr\ConstFetchNode" constant expr
!!    ession.
!!
```

Commits
-------

03cc607 [TypeInfo] Fix handling `ConstFetchNode`

…faultContext (dmbrson)

This PR was squashed before being merged into the 6.4 branch.

Discussion
----------

[Serializer] Fix collect_denormalization_errors flag in defaultContext

| Q             | A
| ------------- | ---
| Branch?       | 6.4
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Issues        | Fix #59721
| License       | MIT

When using the `COLLECT_DENORMALIZATION_ERRORS` flag during denormalization, Symfony should collect **all errors** and report them together in a `PartialDenormalizationException`.

Here is an example with two expected errors:

```php
final readonly class Foo
{
    public function __construct(
        public string $bar,
        public \DateTimeInterface $createdAt,
    ) {}
}

$foo = $this->denormalizer->denormalize(
    data: ['createdAt' => ''],
    type: Foo::class,
);
```

Expected errors
1. `Failed to create object because the class misses the "bar" property.`
2. `The data is either not a string, an empty string, or null; you should pass a string that can be parsed with the passed format or a valid DateTime string.`

---

When the flag is passed via the `context`

```php
$foo = $this->denormalizer->denormalize(
    data: ['createdAt' => ''],
    type: Foo::class,
    context: [
        DenormalizerInterface::COLLECT_DENORMALIZATION_ERRORS => true,
    ],
);
```

Both errors are correctly collected and returned.

When the flag is set via `default_context` in `framework.yaml`:

```yaml
serializer:
    default_context:
        collect_denormalization_errors: true
```

Only one error is returned:
`The data is either not a string, an empty string, or null; you should pass a string that can be parsed with the passed format or a valid DateTime string.`

#Root Cause
The issue originates in the` \src\Symfony\Component\Serializer\Serializer.php`,
`function normalize` :

```php
if (isset($context[DenormalizerInterface::COLLECT_DENORMALIZATION_ERRORS]) || isset($this->defaultContext[DenormalizerInterface::COLLECT_DENORMALIZATION_ERRORS])) {
    unset($context[DenormalizerInterface::COLLECT_DENORMALIZATION_ERRORS]);
    $context['not_normalizable_value_exceptions'] = [];
    $errors = &$context['not_normalizable_value_exceptions'];
    $denormalized = $normalizer->denormalize($data, $type, $format, $context);
}
```

The first time this block is hit, it checks for the flag either in $context or $defaultContext. If found, it initializes the error array with:

```php
    $context['not_normalizable_value_exceptions'] = [];
```
However, during nested denormalization (e.g., when parsing the `createdAt` field), Symfony re-enters this code path. If the flag was provided via `defaultContext`, it is still present on re-entry. Therefore, the `not_normalizable_value_exceptions` array is reset again, losing the previously collected errors.

#My Fix

The fix is to enhance the condition with an additional check to ensure the array of errors is not already initialized:
```php
if (
    (isset($context[DenormalizerInterface::COLLECT_DENORMALIZATION_ERRORS]) || isset($this->defaultContext[DenormalizerInterface::COLLECT_DENORMALIZATION_ERRORS]))
    && !isset($context['not_normalizable_value_exceptions'])
)
```

This ensures the array is only initialized once, preserving previously collected errors in recursive calls, regardless of whether the flag was passed via context or default_context.

Commits
-------

d4a71ee [Serializer] Fix collect_denormalization_errors flag in defaultContext

* 6.4:
  [Console] Table counts wrong column width when using colspan and `setColumnMaxWidth()`
  [Console] Table counts wrong number of padding symbols in `renderCell()` method when cell contain unicode variant selector
  [Cache] Fix using a `ChainAdapter` as an adapter for a pool
  [Serializer] Fix collect_denormalization_errors flag in defaultContext
  [VarDumper] Avoid deprecated call in PgSqlCaster
  Fix command option mode (InputOption::VALUE_REQUIRED)
  [Uid] Improve entropy of the increment for UUIDv7

* 7.2:
  -
  [Console] Table counts wrong column width when using colspan and `setColumnMaxWidth()`
  [Console] Table counts wrong number of padding symbols in `renderCell()` method when cell contain unicode variant selector
  [Cache] Fix using a `ChainAdapter` as an adapter for a pool
  [Serializer] Fix collect_denormalization_errors flag in defaultContext
  [TypeInfo] Fix handling `ConstFetchNode`
  [VarDumper] Avoid deprecated call in PgSqlCaster
  Fix command option mode (InputOption::VALUE_REQUIRED)
  use an EOL-agnostic approach to parse class uses
  [Uid] Improve entropy of the increment for UUIDv7
  [HttpKernel] Fix `#[MapUploadedFile]` handling for optional file uploads