Pierre
Pierre
Forgot to mention: PHP validation for this project is configured to PHP 8.0, fun fact, when switching to PHP 8.2, I don't have warnings in most case, except this one,...
> Can you prepare? I'm sure to understand the question here ?
I noticed a few issues with `use ... as` as well as with using a full namespace such as `use Symfony\Validation\ as Assert`...
Same here, it's a very old bug, I always hit refresh at each file or folder manipulation I do since I use PDT.
> Hi, I have some suggestions. I think that in the attributes, the use of "Map" is redundant (MapTo, MapWith, MapIf, etc..). I think you can drop the "Map" prefix...
If I understood it well, by design, a class can be mapped only to one another class ? Isn't it a very drastic limitation ? I could want to map...
> That's why I suggested the `...classes: {B::class, C::class}`. This way, you could map an object to multiple objects at the same time, and even have different mapping per object...
> To answer your second question, I've implemented the following proposal: > > ``` > #[Map(to: Foo::class, if: 'someconditionistrue')] > #[Map(to: Baz::class, if: 'someconditionistrue')] > class Bar {} > ```...
> @pounard the exact same way on properties: OK, it will probably work fine, but as soon as you'll have many target classes, it's going to make it difficult to...
I would add that what bothers me most is that there is no component for defining mappings between mapping and actual mapper. The attribute reading is hardcoded into the `AutoMapper`...