TYPO3 Core

Tobias Braumann wrote:

Half day is gone and i couldn't find any good solution for my problem without writing my own validator or ended up with a second model.

First i want to describe my problem here. This are my models:

My order has to address properties, one for shipping (mandatory) and one for the billing (optional). The address model has some mandatory fields. There is a checkbox to show the billing address. Everthing works out of the box if
the user need both addresses. But in the case the shipping address and the billing address are the same, he only has to fill out the first address fields.

I know i could write my own validator, but than i have to check all my address properties by my self, and i thought about a solution to turn off the validtor for the property billlingAddress when the checkbox is not set. And i think the best
place for the would be the initilize*Actions

There should be an easy way to do that, similar to the propertyMappingConfiguration.

Pseudocode inside an initilize*Action:

[...]

By the way, this would give us a more dynamic way for validation for specific actions, without the need to write a own model validator for smaller problems like this. Or did I overlooked anything?

I think this is good as it is. Your use case clearly calls for two different object-level validators which validate properties differently based on - just as an example - another property in the object (e.g. "is shipping address"). Once you have that designed correctly, you can apply that validator to your aggregate root's property so that your "Order" object declares two different validators for main and shipping address.

If you have an action that receives the address itself and this action is capable of receiving both these addresses then you may have an additional design problem. But, in order to accommodate this case, you can override the initializeStoreAddressAction (or whatever your action is called) and then make a decision for your validator based on a property in $this->request, then using $this->arguments['address']->setValidator(new MyCustomValidator());

Lastly: it is also possible to define every shared validation in the Address model, as annotations therein - and then create a custom validator for NON-shipping addresses that will validate the additional properties. Then, in your initializeAction, use the same method to switch the validator but instead of using "setValidator" do "addValidator", and only do anything if the address is NOT the shipping address.

On a personal note, I don't think there is any easier way to manipulate this validation and make it dynamic, than exactly creating a custom validator and using it in any of the ways described above. If you agree after reading this, please close the issue ;)

You didn't get the point. I know i could write my own validator, but I don't want do. I still think this would be a nice thing.

Hello Tobias,

I know that you want a super simple solution, but I don't think that we will implement that to extbase. We have a lot of Validators, you can build your own Validators and you can and should use a DomainValidator. That way you have access to all Properties in one Validator. A good start to check, if an address should be validated or not. No need to do nasty things in initialize*Action. So your controller is clean again.

Stefan