프론트엔드 애플리케이션의 오류 처리 마스터하기: 종합 가이드 #37
Merged
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
|
잘봤습니다 렛서~ |
brgndyy
reviewed
Aug 4, 2024
|
|
||
| ### 3장: 왕국 관리 — 오류를 위한 상태 관리 | ||
|
|
||
| 광활한 프론트엔드 개발 왕국에서는 다양한 오류를 만나게 됩니다. 지혜롭고 우아하게 통치하기 위해서는 이러한 오류를 정밀하게 관리해야 합니다. 그럴 때 Redux와 같은 상태 관리 시스템이 필요합니다. |
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.
에러 처리에 관한 글을 번역해 보았습니다.
작성자는 리덕스 사가를 사용해서 서버 상태를 관리했는데, 리액트 쿼리로는 어떻게 짤 수 있을까 상상하면서 읽어보면 좋을 것 같네요!