-
Notifications
You must be signed in to change notification settings - Fork 0
fix: 멘토링 등록 계약과 경력 입력 검증 흐름을 정합하게 수정 #442
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
Merged
Hyeonjun0527
merged 1 commit into
develop
from
refactor/mentoring-registration-sqaush-2
Mar 24, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
🧩 Analysis chain
🌐 Web query:
In react-hook-form, does clearErrors('careerEntries') also clear nested errors like careerEntries.0.description and careerEntries.0.endMonth, or only the root array error?💡 Result:
In react-hook-form, calling clearErrors('careerEntries') clears both the root array error (if any) and all nested errors like careerEntries.0.description and careerEntries.0.endMonth. This is the expected behavior, as confirmed by the official documentation and GitHub issues. The official clearErrors documentation explicitly states: register("test.firstName", { required: true }) register("test.lastName", { required: true }) clearErrors("test") // will clear both errors from test.firstName and test.lastName clearErrors("test.firstName") // for clear single input error This demonstrates that clearing a parent field name removes all errors under that path, including nested ones. GitHub issue
#8476confirms this for field arrays: maintainer@bluebill1049states "This is expected behavior" when clearErrors on a field array root clears nested field errors. They note there's no built-in way to clear only the root without affecting nested errors—you must specify exact nested paths. This behavior has been consistent across versions, with fixes ensuring clearErrors on a path clears the entire subtree (e.g., issues#2730,#2961).Citations:
clearErrors('careerEntries')로 다른 행의 유효성 검사 오류까지 함께 제거됩니다.clearErrors('careerEntries')는 배열 루트 오류뿐만 아니라careerEntries.0.description,careerEntries.0.endMonth같은 중첩 필드의 모든 오류를 함께 제거합니다. 바로 앞의setValue(..., { shouldValidate: true })로 재계산된 다른 행의 유효성 검사 오류가 숨겨져서 검증 흐름이 불일치할 수 있습니다.수정안
🤖 Prompt for AI Agents