Regarding "Add an addRule" about aura.input HOT 6 CLOSED

Alternatively, #40 is a good compromise because it allows develops to write complicated rules within the closure.

from aura.input.

Another idea to add to the discussion is to allow the addition of some sort of AdvancedFilter class which can be allowed to have a range of methods such as:

• addRule($field, $message, $closure)
• setRequired($field, $message)
• mustBeEmail($field, $message)
• etc.

from aura.input.

So for the time being, I've written my own class which extends Filter and implements an addRule() method and a re-written values() method which handles multiple rules per field.

Would you seriously consider the addition of this additional class if I created a pull-request?

This will solve the problem of #39, and I could also merge in #40 too. So the original Filter class is left untouched but gives developers the option of using this new class which provides some extra functionality.

I'm using this library in a large application and would prefer to give back to the community, rather than keeping my own branch/fork. So I'm very happy to put in the work for some kind of solution or compromise.

Many Thanks
Stephen

from aura.input.

Would you seriously consider the addition of this additional class if I created a pull-request?

Sure, let's see the PR.

And thanks for doing the work!

from aura.input.

I think this is taken care of now that #40 is merged. Let me know if there's still trouble.

from aura.input.

Thanks Paul. #40 definitely achieves the same end result :)

from aura.input.