Hi,
I’m curious about the preferred method for communicating errors occurring in a
backend mutation function.
For example, say we have some input from a frontend form that we need to
validate on the backend when we submit this form. We have a mutation function
which carries out form input stat
There's some work still in progress in om.next master around the error
handling story. For the time being you'll have to sort something out
yourself, but the idea is that error handling will eventually be a first
class feature.
David
On Sun, Jun 5, 2016 at 12:46 PM, Max Countryman wrote:
> Hi,
Hi David,
Thanks for letting me know!
In the future, should I expect a server-side mutation function to have the
capability of updating client-side state?
Max
> On Jun 5, 2016, at 12:01, David Nolen wrote:
>
> There's some work still in progress in om.next master around the error
> handlin
That's what server-side mutations do there's nothing to wait for. If you're
talking about some kind of push state thing, there's nothing stopping you
from implementing that today and people already have.
David
On Wed, Jun 8, 2016 at 11:11 AM, Max Countryman wrote:
> Hi David,
>
> Thanks for let
Okay—that was my assumption as well, it just seemed like that wasn’t what was
happening.
I’m still not clear on where a server-side mutation’s value is stored in the
client-side state—when I look at my state atom I don’t seem to see that value
associated with a key.
> On Jun 8, 2016, at 11:08
