We have updated the content of our program. To access the current Software Engineering curriculum visit curriculum.turing.edu.
Error Handling with Fetch
Preface
As front end developers, we should always be concerned about giving our users the best experience possible. One way to that is to make sure that we provide the user with some feedback in case an interaction goes wrong. In this lesson, y’all are going to focus on improving the ui of a form, by providing error messages to our end user.
Warm Up
Let’s review from the Network request GET lesson & Network request POST lesson
In groups, add some stickies to this Jamboard
- What do you remember from request/response cycle?
- what are the response status code when error happens?
The challenge
Visit this repo and follow the directions in the readme carefully to get some practice in gracefully handling errors and presenting them to the end user.
Key takeaways
Common sad paths we want to handle, if possible are:
- Empty states: If there are no items to display. We should let the user know, and maybe give them a CTA button.
- Form submissions:
- Help the user, by not allowing them to pass bad or empty data.
- Make sure that if something goes wrong, ie. a 422 comes back from the server, we let the user know that in a way they can understand
- It’s likely a good idea to have something place in case the server is down as well. This is a great scenario for that
.catchyou’ve likely put at the end of a fetch.
