-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
온보딩 프로젝트 3단계 제출 #3
Open
yoouyeon
wants to merge
32
commits into
main
Choose a base branch
from
jeyoon
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
router.push('/login') 중복 문제
router.push('/login') 중복 문제
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.
21일 금요일 리뷰 중에 있었던 에러 보완하여 제출합니다... 🙂
발생 에러
Error: Abort fetching component for route: "/login"
에러 발생 상황
페이지에 URL로 직접 접근 시도
→ 그 이후 로그아웃
예상 원인
로그아웃 후 login 페이지로 이동을 위해서
router.push('/login')
호출→ 로그아웃 상태이므로
useUser
훅에서error
state가 true로 설정→
DefaultLayout
에서error
가 true이므로 로그인 에러로router.push('/login')
호출→ 에러 발생
해결 방법
DefaultLayout
의useEffect
내부 로직이 실행되는지 (login 페이지는PublicLayout
)위 두가지에 대한 이유를 찾지 못해서...
로그아웃 후에 로그인 페이지로 직접 이동시키지 않고
그 이후에 로그인 에러로 로그인 페이지로 이동되도록 에러만 없애주었습니다... 😕