Skip to content

Commit 5db74af

Browse files
authored
Merge pull request #4098 from vicortez/patch-1
clarification on axios request handling
2 parents ad100a7 + 01920af commit 5db74af

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/2/en/part2d.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -608,7 +608,7 @@ When we try to change the importance of the hardcoded note, we see the following
608608
609609
The application should be able to handle these types of error situations gracefully. Users won't be able to tell that an error has occurred unless they happen to have their console open. The only way the error can be seen in the application is that clicking the button does not affect the note's importance.
610610
611-
We had [previously](/en/part2/getting_data_from_server#axios-and-promises) mentioned that a promise can be in one of three different states. When an HTTP request fails, the associated promise is <i>rejected</i>. Our current code does not handle this rejection in any way.
611+
We had [previously](/en/part2/getting_data_from_server#axios-and-promises) mentioned that a promise can be in one of three different states. When an axios HTTP request fails, the associated promise is <i>rejected</i>. Our current code does not handle this rejection in any way.
612612
613613
The rejection of a promise is [handled](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises) by providing the <em>then</em> method with a second callback function, which is called in the situation where the promise is rejected.
614614

0 commit comments

Comments
 (0)