How not to break the flux concept by doing form validation on the server side?

Question

React

In FLUX all data should only go in one direction [component] -> [dispatcher] -> [store] -> [new data to component]
I have a simple problem. There is a form for editing an order and a list of orders.
The cycle is simple: fill out the form, click add -> [event: create order] -> the dispatcher redirects it to the order storage -> [event in the storage about changes] -> re-rendering the list of orders.
Everything is simple and everything works.
And now to complicate things, we need to validate the order form on the server. When the form has created an event about adding an order, the event intercepts WebAPI and sends it to the server, and if everything is fine, then the event goes to the dispatcher and storage. But if everything is bad and the data is not valid, how to inform the form component about this? In revenge with the event, send a callback to return in case of errors back to the form, then the data no longer goes in one direction.

Answer 1

The solution to this is to use something to manage forms that contains form data and validation statuses, for example look at
https://github.com/christianalfoni/formsy-react
https://github.com/erikras/redux-form
The last one is like more interesting to me

Answer 2

The solution is simple - next to the order data in the store, store also error data for this order. If the api returned validation errors, then store them in the store (this will cause the component to re-render and display errors). When the component is deinitialized, as well as when the call to the api is successfully completed, clean up errors in the store.