Any opinion on this @dunglas @lyrixx @mtarld or anyone else?

Actually, before that PR, paths related to constructor weren't taken into account. And it does look good to me to be more precise in that case

Should we interpret this as an improvement then? For 7.1?

Actually, before that PR, paths related to constructor weren't taken into account. And it does look good to me to be more precise in that case

Should we interpret this as an improvement then? For 7.1?

@nicolas-grekas To me, this seems like a bug. As far as I can tell, the $attributeContext variable was introduced in #39399 for version 5.3, whereas support for collecting type errors was introduced in version 5.4 with #42502. It appears that the wrong variable might have been used by accident 🤷

There's also the fact that the messages actually have the correct paths in them:

            [
...
-                'path' => null,
+                'path' => 'string',
                 'message' => 'Failed to create object because the class misses the "string" property.',
            ],

I agree with @HypeMC, it can be considered as a bugfix in my opinion

Thank you @HypeMC.