hideInitValidationError to true as default value.

[gitana]

hideInitValidationError to true as default value.

[uzquiano]

I agree with this. All those validation messages when the user hasn't done anything yet can be quite intimidating.

We'll get this into the 1.0.4 release.

[drq]

For "Creating New" forms, that is very true. However, for "Editing Existing" forms, we may want to turn it off. Anyway, we will need to do more research before making that change.

At the mean time, you can display the hidden messages using this API in your postRender callback function

renderedForm.showHiddenMessages();

[uzquiano]

I pushed in a change to master so that any views of type 'create' (such as VIEW_WEB_CREATE) will initialize the hideInitValidationError field to true. I also added some examples to the validation-examples.html file. It seems to work pretty well for the cases I've tried.

Just add:

"view": "VIEW_WEB_CREATE"

To your $.alpaca() call and all of the red invalid state boxes will not be rendered on the first pass.

[JocelynDelalande]

Ok, logical enough, but won't do the trick for a non-create form with an ArrayField in which we add (plus button) a new row.

For the record, uzi's commit is 1d92ea3

[uzquiano]

Got it. Okay, sounds like we still have a little more to resolve on this issue.

It sounds like regardless of the view type, when someone clicks "add" on the array toolbar, the new element should have hideInitValidationError true by default. Does that seem correct to you?

That logic should hold for any container field (objects, etc).

[JocelynDelalande]

It sounds like regardless of the view type, when someone clicks "add"
on the array toolbar, the new element should have
hideInitValidationError true by default. Does that seem correct to you?

Yep

[uzquiano]

Added an implementation of this into master along with example.