-
Notifications
You must be signed in to change notification settings - Fork 1
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
Api/kd02109 #64
base: main
Are you sure you want to change the base?
Api/kd02109 #64
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
고생하셨습니다!
keypadToken: string; | ||
}>(URL.USER.keypad, {}, "no-store"); | ||
}>(URL.USER.keypad, {}, "force-cache"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
force-cache
로 변경하신 이유가 궁금합니다. 제가 처음에 세팅했을 때의 의도는, 보안상 키패드는 캐싱없이 새로 받아와야할 것같아서 no-store
로 했었습니다.
setValue(uniqueResiter, !isCheck, { shouldValidate: true }); | ||
} | ||
}; | ||
const onChage = () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
const onChage = () => { | |
const onChange = () => { |
What is this PR?
What has changed?
A notice to reviewers...
Screen