Improvements to validation logic

[gitana]

Improvements to validation logic

[uzquiano]

There have been a number of validation logic updates over the past few days. Here is where we stand today:

#1 - To see the validation logic right away, the form should be loaded with an "edit" view. This is what gets loaded by default. So, by default, users should expect to see validation logic appear right away. (i.e. lots of red boxes on first render)

#2 - To hide the validation logic on first pass, the form should be loaded with a "create" view. You can do this by providing { "view": "VIEW_WEB_CREATE" } or creating your own view. Alternatively, you can hideInitValidationError on any of your fields individually.

#3 - If a field is in a valid state when clicked into, the field will remain in a valid state until the user clicks away (or blurs the field). Upon blur, the field's validation is recomputed and, if invalid, it will highlight with the red box. If the field was originally in an invalid state when clicked into, the field will revalidate on every keyUp() so that if the user enters a valid value, the validation state will clear up right away (i.e. red boxes go away).

#4 - When specifying a form, along with submit buttons, the submit button will be marked disabled until all of the properties of the form are valid. Furthermore, upon clicking the submit button, a recalculation of the form's validity is performed ahead of submitting the post.

Feedback and insights are appreciated. I think we're getting closer to having this right.

[Ognian]

Hello,
my use case is:

1. I create the form with no data, since i'm using VIEW_WEB_EDIT_INLINE I have to set "hideInitValidationError": true on "all" fields
2. Im "filling" the form with setDefault(); setValue(x); the data is correctly filled in, but NOT correctly validated, since validation is not triggered.

Step 2. is repeated multiple times...

.isValid(true) just returns the validation state of the form it thinks the form has .. .validate() does not validate again...
which is the main problem I have with validation now... (tried .renderValidationState() too without success)

What I want to say is that this is still confusing.
Of course there are 2 use cases:

1. Where Data is available at the time of creation, this is how it works now
2. Data is filled in later, this is what is handled by the HideInitValidationError flag on a per Field base

I think that this flag should be on a Form level and not on a field level
I think that this flag has nothing to do with the kind of view used to render the fields.

I think that one view for all fields could also be handled better, but this is a different issue (see #28 )

[StephenOwens-dcat]

I believe that in the case of wizards valdation should only occur for the currently visible fields. URI validation seems to break wizards where the URI fields are on anything other than the first step.

[ripfire44]

The second item doesn't work when I have a submit button on the form. It shows validation message for all after I fill in the first field.
http://jsfiddle.net/35aKD/
If you remove the button property, it works as intended.

[piyushvyas901]

how to put validation on height and width of the image while uploading using alpaca. Can someone please provide me small snippet for it

[mscheper]

re point 2 in @uzquiano's comment from 9 Feb 2013: { "view": "VIEW_WEB_CREATE" } causes this error: The desired view: VIEW_WEB_CREATE could not be loaded. Please make sure it is loaded and not misspelled.

I tried { view: 'web-create' } and { ui: 'web', type: 'create' }, and while neither resulted in an error, neither prevented the error messages from displaying, either. Is there a new way for preventing validation messages from appearing when the form is first rendered?

The Validation API topic says:

An example of this is when the hideInitValidationError flag is set true in the options for the form.

So I tried $myForm.alpaca({ schema: schema, ui: 'web', type: 'create', options: { form: { hideInitValidationError: true } }}), but that still didn't work. Help?