Nicolas Grekas

>> mapping yourself for a specific parameter which does not exist on your entity > > This looks like an edge case with no real life application. ~I don't know...

> If you have been providing an explicit mapping of `[]` yep, this will indeed behave differently if the only outcome you wanted from this mapping was to disable entity-mapping...

Well, we circle back to https://github.com/symfony/symfony/pull/54455#issuecomment-2046855506: if you disabled automapping by default, then you must have added explicit mappings. And if you added an attribute with `mapping: []` explicitly, then...

When there's an id or a match by name, the mapping behavior doesn't change with this PR. What's your point in the end? Do we have a consensus here?

OK, but what's the side effect of this statement in practice? If you don't want any auto-mapping at all, just declare the mappings explicitly, which is already what you do,...

Thanks for the discussion. I came back after a few days of pause on the topic to keep an open mind and I'm happy to propose a new approach, based...

Would you like to give a fix a try? The issue won't fix itself by keeping it open ;)

I guess this can be closed?

I'm proposing to revert this change in https://github.com/symfony/recipes/pull/1302: this breaks the DX, we need to find a better way.

To me this change doesn't make sense BTW: automapping is supposed to be a DX helper. If it is disabled by default, why would anyone want to re-enable it to...