Thoughts on extending foam.String for custom validation

[Joel Hughes]

We are adding validation on fields containing email or phone numbers, for example, via validateObj.  

Obviously we'd like to do this only once. 

Initial thoughts were to 'extend' foam.String with a class such as 'PhoneNumber' with an appropriate validateObj.

This isn't working, validateObj is not entered.

It's been too long since I've fiddled at this level of FOAM, so some ideas/help would be appreciated. 

Thanks

Joel 

[Kevin Greer]

We already have extended String types defined in types.js, like 'PhoneNumber', 'Password', 'Email', etc.

You can set the assertValue Property Property to add validation rules for a Property. It is called when a property is set, after adapt but before preSet.

--
You received this message because you are subscribed to the Google Groups "foam-framework-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to foam-framework-discuss+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Joel Hughes]

Perfect. Thank you.

[Joel Hughes]

When 'in' assertValue, how would one know what property they are?  To determine the property's name or label, for example?

Thanks

Joel 

[Kevin Greer]

assertValue: function(newValue, property) { // this == the object }

So property.name is the property name. 'this' is the object that contains the property. The new/proposed value is passed in as the first argument to the assertValue function.

To unsubscribe from this group and stop receiving emails from it, send an email to foam-framework-discuss+unsubscri...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.