36-fetch-error-handling + MessageMapper + call_update #118
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MartinKavik
force-pushed
the
36-fetch-error-handling
branch
from
6c2bf60
to
0d0ed78
Compare
|
Love the API improvement and customizable error handling! After we test this here for a bit, how do you feel about submitting this to Gloo? |
Good idea, added into my todo list. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#36
I think the best way to explore new Fetch API is to play with
/examples/server_integration(
cargo make start server_integration)Changes
/src/fetch.rsrewritten/examples/server_integrationrewritten/examples/server_interactionupdatedgloo-timersinto rootCargo.tomland removed fromexamples/orders/call_updateand look for implementations of traitMessageMapper