@alborq it's not configurable, however you're free to register your own property access depending on the task.

Yesterday I was talking about this exact same feature with a Symfony developer who would have need this feature in his project.

Somehow related to #19374 (comment)

Not sure how possible it is to rename your property, but couldn't you just rename your accessor to hasAbilityToPrintOnPhotoPaper() or isAbleToPrintOnPhotoPaper() and setter to setAbilityToPrintOnPhotoPaper() or setAbleToPrintOnPhotoPaper()?

@patrick-mcdougle sure i can, but you know like me, it's complex to find a good name of all properties, and in this case, we can find other good name like your exemple, but i thinks in specific case, link with job specification, we cant change name.

I'm not locked with this issue, i just thinks, it can be a problem. (like migrate legacy)

Thank you for this suggestion.
There has not been a lot of activity here for a while. Would you still like to see this feature?

Just a quick reminder to make a comment on this. If I don't hear anything I'll close this.

Hey,

I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen!