David Khourshid

Please create a reproducible example.

I'm open to PRs for this.

Please provide a PR to fix this.

I think both issues can be solved by adding a new form property: `.syncValid` (and maybe `.asyncValid`). The current behavior is that you _should_ be able to submit a form...

Bump: @thomasboyt do you think your use case will be solved with `.syncValid` and `.asyncValid`?

Please use `` and not ``, and let me know if your problem disappears.

Hmm, this is more something that hasn't exactly been considered. Here's a potential way to fix this as an added feature: ```js // future API! dispatch(actions.setFieldsErrors('user.something', { foo: true, bar:...

> as long as it doesn't clear up the errors on page navigation (remount)... Right, it would only clear transient errors when an `actions.change` action for that model is dispatched.

> I have tried the piece of advice that you has mentioned using { transient: true } but didn't work. That's coming up in a future version.

Sorry @jjmr I've been extremely busy - if you know how `transient` can be implemented (should be straightforward) I'd be glad to review and accept such a PR as soon...