Convenience class method to call the fieldValueForObject() instance method you define in your subclass.

Invoked by a field whenever a validator is attached to the field.

The passed validatorKey can be a validator instance, a validator class or a string naming a validator. To make your validator visible, you should name your validator under the SC.Validator base. for example SC.Validator.Number would get used for the 'number' validator key.

This understands validatorKey strings in the following format: 'key' or 'multiple_words' will find validators Key and MultipleWords if you want to share a single validator among multiple fields (for example to validate that two passwords are the same) set a name inside brackets. i.e. 'password[pwd]'.

Convenience class method to call the objectForFieldValue() instance method you define in your subclass.

Called on all validators when they are attached to a field.

You can use this to do any setup that you need. The default does nothing.

Called on a validator just before it is removed from a field. You can tear down any setup you did for the attachTo() method.

Returns the value to set in the field for the passed object value.

The form and view to be set MAY (but will not always) be passed also. You should override this method to help convert an input object into a value that can be displayed by the field. For example, you might convert a date to a property formatted string or a number to a properly formatted value.

Returns the object value for the passed string.

The form and view MAY (but wil not always) be passed also. You should override this method to convert a field value, such as string, into an object value suitable for consumption by the rest of the app. For example you may convert a string into a date or a number.

Validate the field value.

You can implement standard behavior for your validator by using the validate() and validateError() methods. validate() should return NO if the field is not valid, YES otherwise. If you return NO from this method, then the validateError() method will be called so you can generate an error object describing the specific problem.

Invoked just before the user ends editing of the field.

This is a primitive validation method. You can implement the two higher-level methods (validate() and validateError()) if you prefer.

The default implementation calls your validate() method and then validateError() if validate() returns NO. This method should return SC.VALIDATE_OK if validation succeeded or an error object if it fails.

Returns an error object if the field is invalid.

This is the other standard validator method that can be used to implement basic validation. Return an error object explaining why the field is not valid. It will only be called if validate() returned NO.

The default implementation of this method returns a generic error message with the loc string "Invalid.Generate({fieldValue})". You can simply define this loc string in strings.js if you prefer or you can override this method to provide a more specific error message.

Invoked when the user presses a key.

This method is used to restrict the letters and numbers the user is allowed to enter. You should not use this method to perform full validation on the field. Instead use validatePartial().

Invoked 1ms after the user types a key (if a change is allowed).

You can use this validate the new partial string and return an error if needed. The default will validate a partial only if there was already an error. This allows the user to try to get it right before you bug them.

Unlike the other methods, you should return SC.VALIDATE_NO_CHANGE if you did not actually validate the partial string. If you return SC.VALIDATE_OK then any showing errors will be hidden.

Invoked just before the form is submitted.

This method gives your validators one last chance to perform validation on the form as a whole. The default version does the same thing as the validateChange() method.