Would be nice if this would also support ignoring properties based on a prefix, like mentioned in this comment related to generated 'withXX' methods.

I'll try to see it on the weekend.

@diversit i'm add prefix for Ignored annotation for this case

Awesome!

Would be nice if this would also support ignoring properties based on a prefix, like mentioned in #1958 (comment) related to generated 'withXX' methods.

@diversit we do not want to support pattern ignores. We've said this few times already.

@xumk your idea with the prefix is OK I think, it basically transforms customer.firstName, customer.lastName to something more simpler. Unless, I am not seeing it properly

@filiphr
I assumed exactly this use
@Ignored( prefix = "animal", targets = { "publicAge", "size", "publicColor", "age", "color" } )
just added a prefix with dot to the properties. It is more convenient than writing targets = { "animal.publicAge", "animal.size", "animal.publicColor"...etc
but nothing prevents you from writing it down according to the standard

@filiphr thanks. i fixed remarks and checked you case

@Mapping(target = "name", ignore = true)
@Ignored(targets = "name")

it test ok. property is ignored.

@Mapping(target = "name", source = "firstName")
@Ignored(targets =  "name")

it not ignored property. name have value firstName. Is it good?

i added two test

Thanks for checking that @xumk. My main point was the fact that a combination of @Mapping and @Ignored for the same property should not be allowed, we should have an error if such a thing happens. The same as if we are using the same target in @Mapping

@filiphr ok, I will try to do it soon.

@filiphr I added a check