[#171] Protect route on client side #259
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
|
🚀 Storybook preview: https://65efde01a0f7c06627626a14--cheerful-pothos-666fe1.netlify.app |
isutare412
reviewed
Mar 12, 2024
|
🚀 Storybook preview: https://65f0000b57bced7e49c1a940--cheerful-pothos-666fe1.netlify.app |
2wheeh
force-pushed
the
feature/issue-171/protect-route
branch
from
4f0fe89 to
3094212
Compare
|
🚀 Storybook preview: https://65f0318fd7e1faa5872aabf0--cheerful-pothos-666fe1.netlify.app |
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.
#171
Changes
Auth Context 에서 protectedPaths 에 접근 시 유효한 토큰으로 로그인 되어있는지 확인합니다.
이전에 논의한 대로 일단은 클라이언트 사이드에서 auth 관련 로직을 모두 처리합니다.
따라서 페이지 가드 역시 클라이언트 사이드에서 이뤄집니다.
백엔드를 통해 유효한 유저인지 확인되기 전까지의 잠깐동안 SSR 된 컴포넌트가 보여질 수 있습니다.
인증이 필요한 데이터는 애초에 서버사이드에서 다루지 않는 구조이므로, 혹시 어색할 수 있는 유저 경험외에 큰 문제는 없어보입니다.