TYPO3.Fluid

Bastian Waidelich wrote:

But how should the error handling work, if the textbox was not bound to a property?

yes but it has a name and it's bound to the namespaced form so it could be assigned to
appropriate property within the error object.

Nikolas Hagelstein (pulponair) wrote:

yes but it has a name and it's bound to the namespaced form so it could be assigned to
appropriate property within the error object.

Ok, but why wouldn't you just bind it to the property in that case?

Bastian Waidelich wrote:

Nikolas Hagelstein (pulponair) wrote:

yes but it has a name and it's bound to the namespaced form so it could be assigned to
appropriate property within the error object.

Ok, but why wouldn't you just bind it to the property in that case?

A property would presume an object. Many real world forms do not reference to an object or they consist of a mixture of object fields and addtional fields.
Sample:

<f:form controller="AnyController" action="index" object="{user}" name="user" id="userForm">
  <f:form.textbox property="username" />
  <f:form.textbox property="password" />
  <f:form.textbox name="passwordConfirmation" />
</form>

In this case username and password refere to an object (domain model user).
But passwordConfirmation das not belong to this object at all but needs to be validated as well.

Imagine forms that do not to refere to an object at all. E.g. if the form data contains various Information and real objects are created from this information after the form has been submited succesfully.

Bastian Waidelich wrote:

Ok, I see. But AFAIK the property validation only works for bound objects yet. I'm assigning this to Sebastian for now.

Nope works for controller arguments as well:

@validate $forename notEmpty
public function indexAction($forename.....