Skip to content

Commit

Permalink
Add BO room to error lesson
Browse files Browse the repository at this point in the history
  • Loading branch information
kaylagordon committed Nov 5, 2024
1 parent 1154a1b commit ba1e953
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions module3/lessons/fe_error_handling.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,19 @@ There are four codepens in **[this collection](https://codepen.io/collection/Exq
- Users should know if something went wrong (whether it was user error or not).
- We should wait until after the Promise has successfully resolved from a fetch to confirm the outcome with the user. This is what we will talk about next!

<section class="call-to-action">
### Project Brainstorm

Let's spend 10 minutes in your project teams to brainstorm what error prevention you'd like to add to your projects. It might be helpful to think through these questions:
- What ways can the user currently break things?
- What else could go wrong?
- How can we prevent errors from happening?
- How can we respond to errors after they happen?
- What should the user see when things go right?
- What should the user see when things go wrong?

**At the end of the 10 minutes, please have one person from your team DM your instructor on Slack with a list of what error handling you'd like to add to your project.** This list can include FE and BE error handling.
</section>

## Handling Fetch Errors

Expand Down

0 comments on commit ba1e953

Please sign in to comment.