Allow deserialization error handling in fetch about seed HOT 9 CLOSED

There was some discussion of this in the original PR. It should obviously be done but it seems the implementation will need some thought.

from seed.

I totally agree. A solid solution wasn't super obvious or I would have opened a PR. Just for the sake of furthering the discussion my expectation was to be able to handle the error case and send a Msg just like I did for the success case.

from seed.

Looking at the discussion it seems to revolve primarily around how to handle the two different error types. For my particular use case a new error type that has From implemented for both would be enough. What other options would seem to fit the situation? If an ideal solution could be hashed out I might be able to spare some time to put up a pr.

from seed.

Futures are now returned from update, and their result needs to be Result<Msg, Msg>, so the error case is now passed as a Msg back to the update function.

from seed.

@glademiller does sapir's latest PRs/the 3.0 release resolve this?

from seed.

from seed.

I'll try to fix it.

from seed.

@glademiller Merged PR #118 should resolve your problems - could you provide feedback or/and close the issue?

from seed.

I haven't dug too deep but looking at the code I believe this solves the issues I had. Thank you!

from seed.