TYPO3 Core

The ValidatorResolver tries to resolve the Validator for a model class by testing for naming conventions. This mechanism is not skipped, if the dontvalidate annotation is set. Thus I can not use the naming convention if I have a single action, where the validation is not needed.

Example:

newBookingAction (dontvalidate)

previewBookingAction (dontvalidate) since it shows the current progress

createBookingAction (validate)

My validator is called BookingValidator and is executed each time if an argument of type Tx_MyExt_Domain_Model_Booking is found.

It is possible to rename the Validator and add it explicitly as annotation but ignoring the "dontvalidate" annotation is definitely unexpected behaviour (and it took me half an hour to figure out, where the mistake was...)

I think the $validatorConjunctions with parameter names that are annotated as "dontvalidate" should be ignored.