Forms: validation serverSide & clientSide

[hrach]

In current implementation it's (almost) impossible to add validation, which would generate some validation name for client-side. Let's take a walk.

1. Only way to let Nette Forms generate some client-side validation name is to pass string callback, or some other structure, which is static. Defined here. This means that these examples are only acceptable
   • fnValidator
   • foo\fnValidator -> string -> the name is not "corrected" for js
   • foo\bar::methodValidator -> string -> the name is not "corrected" for js
   • array('MyClass, 'methodValidator')
2. But it is impossible to pass these callback as a validator for Rule.
   • only way is to use NOT-namespace function
   • namespaced function correctly pass this check, however, js fn name is unusable "op":"foo\\mytest".
   • static call doesn't pass through is_callable function here - to be correct, it doesn't pass in array format. In string format such as foo::mytest this function behaves ok... but there is again problem with unusable javascript name ("op":"foo\bar::mytest")

I would like to see some option to name the validation for Javascript.

[dg]

The names are "corrected" for js in netteForms.js http://github.com/nette/nette/blob/89d48b7afba3b1b5bb90a8eae9a2dec6771ac93c/client-side/netteForms.js#L220

[hrach]

How can I missed that? :D

This make it a little bit easier, but I would like to use some non-static callback, couldn't be here implemented something like

if (is_array($op)) {
    $op = get_class($op[0]) . '::' . $op[1]);
}

Otherwise I would close this.

[dg]

I have some plans to improve validation and this will be solved.

[Majkl578]

Unfortunately, that still doesn't solve problem with closures (which are most handful) at all.

[hrach]

@Majk578 ... yes.

[Majkl578]

I'm thinking about automated identifying closures and only possible cross-request solution seems to be declaring filename + line, but that won't work in oneliners. :S Any other idea?