I agree primarily for consistency with other controller attributes, and I also agree that its main purpose is mapping raw input values into an object (DTO), so MapInput makes sense to me.

The problem now is that #[Argument] and #[Option] are in a similar situation, aren't they? and it'll feel inconsistent that two closely related concepts follow different naming conventions in the same context. For instance:

function __invoke(#[MapInput] TestDto $dto, #[Option] bool $test = false)

Both naming conventions are valid to me:

• MapInput focuses on the action/operation around the parameter value,
• Input (same as Argument & Option) broadly reflects the parameter's role.

Even if the reasons explained are completely valid to me, I think consistency should be tied to the component itself first, then to other components and the framework if possible. That's why I choose Input for this attribute.

I agree with your POV as well, I just wanted to share the other side for consideration.