[Question] Save (autosubmit) the form on field changes about uniforms

[radekmie]

Go ahead.

[radekmie]

That's an idea for new functionality. I'll do it asap.

[serkandurusoy]

Wow!!!

I was just tinkering with the idea (in my head tbh) for the past few days and thinking around extending the form and using the onchange event and the state changes within the lifecycle methods.

But it would just be plain awesome if you were to implement it natively.

---

On a not directly related, but somewhat accompanying note:

While at it, it would also be great if you could introduce a pristine prop for both the fields and the form, meaning, if a field value has not changed after the initial render, the field is pristine: true and if none of the fields of the form has yet changed, it woud be pristine: true for the form itself or even contain a list of fields that have changed.

that would allow for fine grained validation handling.

for example, one may not want the whole form to undergo validation before its first actual submit, and then all subsequent "changes" would rerun validation.

it would be much like https://github.com/aldeed/meteor-autoform#fine-tuning-validation

[radekmie]

I've also released 1.0.0-rc.7 on npm.

---

As to the send note - I don't really get you idea of that pristine state, but your example sounds like validate="onChangeAfterSubmit" on ValidatedForm (and descendants), doesn't it?

[serkandurusoy]

@radekmie this was quick! thank you very much.

should I open another issue to further discuss the pristine topic?

[radekmie]

It's fixed in 1.0.0-rc.9.

[serkandurusoy]

Thanks a lot!