Skip to content

Conversation

@YouD0313
Copy link
Collaborator

@YouD0313 YouD0313 commented May 15, 2025

구현내용

디렉토리 변경에 따른 경로 수정

연관이슈

close #295

Summary by CodeRabbit

  • Chores
    • 디렉터리 구조 변경에 따라 여러 컴포넌트와 훅의 import 경로가 일괄적으로 수정되었습니다.
    • 사용자 관련 페이지, 컴포넌트, 훅의 경로가 user 하위 폴더로 이동되었습니다.
    • 코드 동작, 화면, 기능에는 영향이 없으며, 내부 구조 정리에 따른 변경입니다.

@YouD0313 YouD0313 requested a review from layout-SY May 15, 2025 06:30
@YouD0313 YouD0313 self-assigned this May 15, 2025
@YouD0313 YouD0313 added the 🛠개선 성능 개선/리팩토링에 대한 라벨 label May 15, 2025
@YouD0313 YouD0313 linked an issue May 15, 2025 that may be closed by this pull request
1 task
@coderabbitai
Copy link

coderabbitai bot commented May 15, 2025

"""

Walkthrough

이 변경은 사용자 관련 컴포넌트, 훅, 상수, 타입 등의 import 경로를 더 깊은 user 디렉터리 구조로 일괄 수정한 것입니다. 코드 로직, 함수, 컴포넌트의 동작에는 영향이 없으며, 오직 모듈 해석 경로만 새 폴더 구조에 맞게 조정되었습니다.

Changes

파일 그룹/경로 요약 변경 요약
src/components/user/applyComponents/, src/components/user/comment/, src/components/user/customerService/, src/components/user/evaluation/, src/components/user/home/, src/components/user/manageProjects/ 모든 import 경로를 더 깊은 user 디렉터리 구조로 수정. 코드 로직, props, 렌더링에는 영향 없음.
src/hooks/user/CommentHooks/, src/hooks/user/ProjectHooks/, src/hooks/user/evaluationHooks/, src/hooks/user/ API, 모델, 상수, 훅의 import 경로를 한 단계 더 깊은 디렉터리로 수정. 내부 로직 변경 없음.
src/routes/AppRoutes.tsx 모든 lazy load 컴포넌트 및 ROUTES 상수 import 경로를 user 하위 디렉터리로 변경. 라우팅 로직 불변.

Sequence Diagram(s)

(해당 변경은 경로 구조만 변경되어 시퀀스 다이어그램 생략)

Assessment against linked issues

Objective (이슈 번호) Addressed Explanation
관리자 페이지를 위한 경로 세팅 (#295)

Possibly related PRs

Poem

새로 짠 경로, 토끼가 뛰노네
user 폴더 깊숙이, 모듈들이 모여드네
로직은 그대로, 길만 바꿔주니
깔끔한 구조에 코드도 웃지
hop hop! 경로 따라
🐇
오늘도 리팩터링, 토끼 발자국 남긴다!

"""

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5a50962 and eabe2fa.

📒 Files selected for processing (4)
  • src/components/common/ProtectRoute.tsx (1 hunks)
  • src/components/common/modal/Modal.tsx (1 hunks)
  • src/components/common/sidebar/editMyProfileImg/EditMyProfileImg.tsx (1 hunks)
  • src/components/common/skillTagBox/SkillTagBox.tsx (1 hunks)
✅ Files skipped from review due to trivial changes (4)
  • src/components/common/skillTagBox/SkillTagBox.tsx
  • src/components/common/sidebar/editMyProfileImg/EditMyProfileImg.tsx
  • src/components/common/ProtectRoute.tsx
  • src/components/common/modal/Modal.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: accessibility-test
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 11

🔭 Outside diff range comments (1)
src/hooks/user/ProjectHooks/useApplyProject.ts (1)

12-15: 🛠️ Refactor suggestion

중복된 import 문을 정리해야 합니다.

이 파일의 import 문들이 중복되어 있습니다. 병합 충돌이 해결된 후에는 중복된 import 문을 제거해야 합니다.

-import { navigate } from 'react-router-dom';
-import { postApplicantProject } from '../../../api/joinProject.api';
-import { joinProject } from '../../../models/joinProject';
-import { MODAL_MESSAGE } from '../../../constants/user/modalMessage';
-import { ROUTES } from '../../../constants/user/routes';
+import { navigate } from 'react-router-dom';

충돌이 해결된 후 위에서 import된 모듈들은 아래에서 다시 import할 필요가 없습니다.

🧰 Tools
🪛 Biome (1.9.4)

[error] 12-12: Shouldn't redeclare 'postApplicantProject'. Consider to delete it or rename it.

'postApplicantProject' is defined here:

(lint/suspicious/noRedeclare)


[error] 13-13: Shouldn't redeclare 'joinProject'. Consider to delete it or rename it.

'joinProject' is defined here:

(lint/suspicious/noRedeclare)


[error] 14-14: Shouldn't redeclare 'MODAL_MESSAGE'. Consider to delete it or rename it.

'MODAL_MESSAGE' is defined here:

(lint/suspicious/noRedeclare)


[error] 15-15: Shouldn't redeclare 'ROUTES'. Consider to delete it or rename it.

'ROUTES' is defined here:

(lint/suspicious/noRedeclare)

🧹 Nitpick comments (6)
src/components/user/manageProjects/applicantInfo/ApplicantInfo.tsx (2)

2-3: 깊어진 상대 경로 import 확인 및 유지보수성 제안
현재 변경된 상대 경로(../../../../models/applicant, ../../../common/avatar/AvatarList)는 올바르게 반영되어 있습니다. 다만 깊은 상대 경로는 가독성과 유지보수성을 저하시킬 수 있으므로 tsconfig.json의 path alias(@models/applicant, @common/avatar 등) 도입을 고려해 보시길 추천드립니다.


5-5: formatDate 유틸 import 경로 업데이트
../../../../util/format로 경로가 정확히 수정되었습니다. 동일한 맥락에서 경로 alias 사용을 검토하면 전반적인 가독성이 향상될 수 있습니다.

src/components/user/comment/DropDownItem.tsx (1)

1-3: 깊어진 import 경로 확인 & alias 도입 검토
../../../hooks/user/CommentHooks/useDeleteComment, ../../../hooks/user/CommentHooks/useDeleteReply, ../../../hooks/useModal 경로가 올바르게 업데이트되었습니다. 반복되는 깊은 상대 경로 대신 @hooks/user/CommentHooks 또는 @hooks와 같은 alias 설정을 활용하면 가독성과 유지보수성이 향상됩니다.

src/components/user/manageProjects/Card.tsx (1)

2-4: 깊은 상대 경로 import & alias 도입 제안
../../../models/manageMyProject, ../../common/avatar/AvatarList, ../../../util/formatDate 경로가 정상적으로 반영되었습니다. tsconfig path alias(@models/manageMyProject, @common/avatar, @util/formatDate 등)를 설정해 경로 관리를 간소화하는 방안을 고려해 보세요.

src/hooks/user/useAlarmDelete.ts (1)

2-2: 상대 경로 import 업데이트 및 alias 제안
../../api/alarm.api, ../../store/authStore 경로가 올바르게 수정되었습니다. 깊은 상대 경로를 줄이기 위해 @api/alarm 또는 @store/auth 등 path alias 사용을 검토해 보시기 바랍니다.

Also applies to: 4-4

src/components/user/customerService/noticeDetail/content/NoticeDetailContent.tsx (1)

2-2: 깊은 상대 경로 import 개선 제안
../../../../../util/format, ../../../../common/contentBorder/ContentBorder 경로가 정확히 반영되었으나, 지나치게 깊은 상대 경로는 유지보수에 부담을 줍니다. tsconfig path alias를 도입해 @util/format, @common/contentBorder 등으로 간소화하는 것을 추천드립니다.

Also applies to: 5-5

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2e6a0dc and f9388b9.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (61)
  • src/components/user/applyComponents/careersComponent/CareersComponent.tsx (1 hunks)
  • src/components/user/applyComponents/phoneComponent/PhoneComponent.tsx (1 hunks)
  • src/components/user/comment/CommentLayout.tsx (1 hunks)
  • src/components/user/comment/DropDownItem.tsx (1 hunks)
  • src/components/user/comment/commentComponent/CommentComponentLayout.tsx (1 hunks)
  • src/components/user/comment/commentInput/CommentInput.tsx (1 hunks)
  • src/components/user/comment/replyComponent/ReplyComponent.tsx (1 hunks)
  • src/components/user/customerService/MoveInquiredLink.tsx (1 hunks)
  • src/components/user/customerService/faq/FAQContent.tsx (1 hunks)
  • src/components/user/customerService/inquiry/Inquiry.tsx (1 hunks)
  • src/components/user/customerService/notice/NoticeList.tsx (1 hunks)
  • src/components/user/customerService/noticeDetail/NoticeDetailBundle.tsx (1 hunks)
  • src/components/user/customerService/noticeDetail/bottom/NoticeDetailBottom.tsx (1 hunks)
  • src/components/user/customerService/noticeDetail/bottom/button/ListButton.tsx (1 hunks)
  • src/components/user/customerService/noticeDetail/bottom/button/OtherNoticeButton.tsx (1 hunks)
  • src/components/user/customerService/noticeDetail/content/NoticeDetailContent.tsx (1 hunks)
  • src/components/user/evaluation/EvaluationContent.tsx (1 hunks)
  • src/components/user/home/projectCardLists/ProjectCardLists.tsx (1 hunks)
  • src/components/user/home/projectCardLists/cardList/CardList.tsx (1 hunks)
  • src/components/user/home/projectStats/ProjectStats.tsx (1 hunks)
  • src/components/user/home/searchFiltering/filteringContents/FilteringContents.tsx (1 hunks)
  • src/components/user/home/searchFiltering/search/Search.tsx (1 hunks)
  • src/components/user/manageProjects/Card.tsx (1 hunks)
  • src/components/user/manageProjects/CardList.tsx (1 hunks)
  • src/components/user/manageProjects/ProjectHeader.tsx (1 hunks)
  • src/components/user/manageProjects/RecruitmentDate.tsx (1 hunks)
  • src/components/user/manageProjects/applicantInfo/ApplicantInfo.tsx (1 hunks)
  • src/components/user/manageProjects/applicantList/ApplicantItem.tsx (1 hunks)
  • src/components/user/manageProjects/applicantList/ApplicantList.tsx (1 hunks)
  • src/components/user/manageProjects/passNonPassList/PassNonPassItem.tsx (1 hunks)
  • src/components/user/manageProjects/passNonPassList/PassNonPassList.tsx (1 hunks)
  • src/hooks/user/CommentHooks/useDeleteComment.ts (1 hunks)
  • src/hooks/user/CommentHooks/useDeleteReply.ts (1 hunks)
  • src/hooks/user/CommentHooks/useGetComment.ts (1 hunks)
  • src/hooks/user/CommentHooks/useGetReply.ts (1 hunks)
  • src/hooks/user/CommentHooks/usePatchReply.ts (1 hunks)
  • src/hooks/user/CommentHooks/usePostComment.ts (1 hunks)
  • src/hooks/user/CommentHooks/usePostReply.ts (1 hunks)
  • src/hooks/user/CommentHooks/usePutComment.ts (1 hunks)
  • src/hooks/user/ProjectHooks/useApplyProject.ts (1 hunks)
  • src/hooks/user/ProjectHooks/useCreateProject.ts (1 hunks)
  • src/hooks/user/ProjectHooks/useTagSelectors.ts (1 hunks)
  • src/hooks/user/ProjectHooks/useUpdateProject.ts (1 hunks)
  • src/hooks/user/evaluationHooks/useEvaluationStep.ts (1 hunks)
  • src/hooks/user/evaluationHooks/useGetEvaluation.ts (1 hunks)
  • src/hooks/user/evaluationHooks/usePostEvaluation.ts (1 hunks)
  • src/hooks/user/useAlarmDelete.ts (1 hunks)
  • src/hooks/user/useAlarmList.ts (1 hunks)
  • src/hooks/user/useAlarmPatch.ts (1 hunks)
  • src/hooks/user/useApllicantList.ts (1 hunks)
  • src/hooks/user/useApplicantInfo.ts (1 hunks)
  • src/hooks/user/useChartData.ts (1 hunks)
  • src/hooks/user/useEmailVerification.ts (1 hunks)
  • src/hooks/user/useGetFAQ.ts (1 hunks)
  • src/hooks/user/useGetMyComments.ts (1 hunks)
  • src/hooks/user/useGetMyInquiries.ts (1 hunks)
  • src/hooks/user/useGetNotice.ts (1 hunks)
  • src/hooks/user/useGetNoticeDetail.ts (1 hunks)
  • src/hooks/user/useGetProjectData.ts (1 hunks)
  • src/pages/user/home/Home.tsx (1 hunks)
  • src/routes/AppRoutes.tsx (1 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
src/hooks/user/ProjectHooks/useTagSelectors.ts

[error] 8-8: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

src/hooks/user/ProjectHooks/useUpdateProject.ts

[error] 8-9: Expected a statement but instead found '======='.

Expected a statement here.

(parse)


[error] 16-16: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)


[error] 10-10: Shouldn't redeclare 'putProject'. Consider to delete it or rename it.

'putProject' is defined here:

(lint/suspicious/noRedeclare)


[error] 11-11: Shouldn't redeclare 'managedProjectKey'. Consider to delete it or rename it.

'managedProjectKey' is defined here:

(lint/suspicious/noRedeclare)


[error] 12-12: Shouldn't redeclare 'FormData'. Consider to delete it or rename it.

'FormData' is defined here:

(lint/suspicious/noRedeclare)


[error] 13-13: Shouldn't redeclare 'MODAL_MESSAGE'. Consider to delete it or rename it.

'MODAL_MESSAGE' is defined here:

(lint/suspicious/noRedeclare)


[error] 14-14: Shouldn't redeclare 'ROUTES'. Consider to delete it or rename it.

'ROUTES' is defined here:

(lint/suspicious/noRedeclare)

src/hooks/user/evaluationHooks/usePostEvaluation.ts

[error] 5-6: Expected a statement but instead found '======='.

Expected a statement here.

(parse)


[error] 10-10: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)


[error] 7-7: Shouldn't redeclare 'postEvaluation'. Consider to delete it or rename it.

'postEvaluation' is defined here:

(lint/suspicious/noRedeclare)


[error] 8-8: Shouldn't redeclare 'ProjectMemberListEval'. Consider to delete it or rename it.

'ProjectMemberListEval' is defined here:

(lint/suspicious/noRedeclare)


[error] 9-9: Shouldn't redeclare 'apiEvaluatedUser'. Consider to delete it or rename it.

'apiEvaluatedUser' is defined here:

(lint/suspicious/noRedeclare)

src/components/user/applyComponents/careersComponent/CareersComponent.tsx

[error] 6-7: Expected a statement but instead found '======='.

Expected a statement here.

(parse)


[error] 12-12: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)


[error] 8-8: Shouldn't redeclare 'ApplySchemeType'. Consider to delete it or rename it.

'ApplySchemeType' is defined here:

(lint/suspicious/noRedeclare)


[error] 9-9: Shouldn't redeclare 'S'. Consider to delete it or rename it.

'S' is defined here:

(lint/suspicious/noRedeclare)


[error] 10-10: Shouldn't redeclare 'CareerInput'. Consider to delete it or rename it.

'CareerInput' is defined here:

(lint/suspicious/noRedeclare)


[error] 11-11: Shouldn't redeclare 'CAREER_INPUT'. Consider to delete it or rename it.

'CAREER_INPUT' is defined here:

(lint/suspicious/noRedeclare)

src/components/user/applyComponents/phoneComponent/PhoneComponent.tsx

[error] 5-5: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

src/pages/user/home/Home.tsx

[error] 9-9: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

src/hooks/user/ProjectHooks/useCreateProject.ts

[error] 8-9: Expected a statement but instead found '======='.

Expected a statement here.

(parse)


[error] 16-16: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)


[error] 10-10: Shouldn't redeclare 'postProject'. Consider to delete it or rename it.

'postProject' is defined here:

(lint/suspicious/noRedeclare)


[error] 11-11: Shouldn't redeclare 'MODAL_MESSAGE'. Consider to delete it or rename it.

'MODAL_MESSAGE' is defined here:

(lint/suspicious/noRedeclare)


[error] 12-12: Shouldn't redeclare 'managedProjectKey'. Consider to delete it or rename it.

'managedProjectKey' is defined here:

(lint/suspicious/noRedeclare)


[error] 13-13: Shouldn't redeclare 'ROUTES'. Consider to delete it or rename it.

'ROUTES' is defined here:

(lint/suspicious/noRedeclare)


[error] 14-14: Shouldn't redeclare 'FormData'. Consider to delete it or rename it.

'FormData' is defined here:

(lint/suspicious/noRedeclare)

src/hooks/user/evaluationHooks/useEvaluationStep.ts

[error] 6-6: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

src/hooks/user/evaluationHooks/useGetEvaluation.ts

[error] 5-5: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

src/hooks/user/ProjectHooks/useApplyProject.ts

[error] 3-4: Expected a statement but instead found '======='.

Expected a statement here.

(parse)


[error] 10-10: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)


[error] 6-6: Shouldn't redeclare 'ProjectListKey'. Consider to delete it or rename it.

'ProjectListKey' is defined here:

(lint/suspicious/noRedeclare)


[error] 6-6: Shouldn't redeclare 'userInfoKey'. Consider to delete it or rename it.

'userInfoKey' is defined here:

(lint/suspicious/noRedeclare)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: accessibility-test
🔇 Additional comments (52)
src/components/user/manageProjects/RecruitmentDate.tsx (1)

1-2: import 경로 정상 확인

ProjectDetailPlusformatDate 모듈을 가져오는 상대 경로(../../../models/projectDetail, ../../../util/formatDate)가 RecruitmentDate.tsx 위치 기준으로 올바르게 설정되어 있습니다. 로직에 영향이 없으므로 승인합니다.

src/components/user/manageProjects/applicantList/ApplicantItem.tsx (1)

2-2: import 경로 정상 확인

ApplicantInfo 타입을 가져오는 상대 경로(../../../../models/applicant)가 현재 폴더 구조에 맞춰 정확하게 수정되었습니다. 로직 변화가 없으므로 승인합니다.

src/hooks/user/useEmailVerification.ts (1)

2-2: import 경로 정상 확인

postVerificationEmailpostVerifyEmailCode를 불러오는 상대 경로(../../api/auth.api)가 useEmailVerification.ts 위치 기준으로 올바르게 설정되어 있습니다. 기능에 영향이 없으므로 승인합니다.

src/components/user/customerService/noticeDetail/NoticeDetailBundle.tsx (1)

2-2: import 경로 정상 확인

useGetNoticeDetail 훅을 가져오는 상대 경로(../../../../hooks/user/useGetNoticeDetail)가 현재 디렉토리 구조에 부합합니다. 로직 변화 없이 승인합니다.

src/hooks/user/useGetProjectData.ts (1)

3-3: 경로 수정 확인
디렉토리 구조 변경에 따라 getProjectData import 경로가 정상적으로 업데이트되었습니다.

src/hooks/user/CommentHooks/useDeleteComment.ts (1)

3-3: 경로 수정 확인
deleteComment import 경로가 변경된 디렉토리 구조에 맞게 올바르게 조정되었습니다.

src/hooks/user/useGetMyInquiries.ts (1)

2-3: 경로 수정 확인
getMyInquiriesuseAuthStore import 경로가 새로운 디렉토리 구조에 맞추어 정상적으로 업데이트되었습니다.

src/hooks/user/CommentHooks/usePostReply.ts (1)

2-2: 경로 수정 확인
postReply import 경로가 변경된 디렉토리 구조에 맞게 올바르게 조정되었습니다.

src/components/user/customerService/faq/FAQContent.tsx (1)

2-2: 경로 수정 확인
FAQ 타입 import 경로가 새로운 디렉토리 구조에 맞추어 정상적으로 업데이트되었습니다.

src/components/user/manageProjects/applicantList/ApplicantList.tsx (1)

2-2: import 경로가 새로운 디렉토리 구조에 맞게 올바르게 수정되었습니다.
변경된 상대 경로(../../../../models/applicant)가 ApplicantList 위치에서 src/models/applicant로 정확하게 연결됩니다.

src/hooks/user/useGetNoticeDetail.ts (1)

2-2: import 경로가 디렉토리 재구조화에 맞게 업데이트되었습니다.
useGetNoticeDetail 훅 위치에서 src/api/customerService.api로 가리키는 상대 경로(../../api/customerService.api)가 정확합니다.

src/hooks/user/useApllicantList.ts (1)

3-4: getApplicantList 및 ApiApplicants import 경로가 정확히 반영되었습니다.
훅 파일(src/hooks/user/useApllicantList.ts)에서 ../../api/applicant.api../../models/applicant로 올바르게 업데이트되어, 새로운 디렉토리 구조와 일치합니다.

src/hooks/user/useAlarmList.ts (1)

3-4: getAlarmList 및 useAuthStore import 경로가 올바르게 조정되었습니다.
useAlarmList 훅에서 ../../api/alarm.api../../store/authStore로 변경된 경로가 새로운 디렉토리 깊이에 맞춰 정확합니다.

src/hooks/user/CommentHooks/useGetComment.ts (1)

2-2: getComment import 경로가 디렉토리 변경을 반영하도록 수정되었습니다.
useGetComment 훅에서 ../../../api/comment.api로 올바르게 업데이트되어, src/api/comment.api로 정확히 연결됩니다.

src/hooks/user/CommentHooks/usePatchReply.ts (1)

2-2: import 경로가 올바르게 수정되었습니다.
putReply의 import 경로가 새 디렉토리 구조에 맞추어 ../../../api/reply.api로 변경되어 있으며, 기능에 영향이 없습니다.

src/components/user/customerService/noticeDetail/bottom/button/OtherNoticeButton.tsx (1)

1-3: import 경로가 일관되게 업데이트되었습니다.
ROUTES, OtherNotice, formatDate의 import 경로가 새 디렉토리 구조에 맞춰 올바른 깊이로 변경되었으며, 컴포넌트 로직에 영향이 없습니다.

src/hooks/user/CommentHooks/useGetReply.ts (1)

3-3: import 경로가 올바르게 수정되었습니다.
getReply 함수의 import 경로가 ../../../api/reply.api로 변경되어 디렉토리 재구조화에 부합합니다.

src/components/user/home/searchFiltering/search/Search.tsx (1)

4-4: import 경로가 일관성 있게 수정되었습니다.
useSaveSearchFiltering 훅의 경로가 디렉토리 구조 변경에 맞춰 ../../../../../hooks/user/useSaveSearchFiltering로 업데이트되었습니다.

src/hooks/user/CommentHooks/usePutComment.ts (1)

2-2: import 경로가 올바르게 업데이트되었습니다.
patchComment 함수의 경로가 ../../../api/comment.api로 변경되어 디렉토리 구조 변경에 맞춰져 있습니다.

src/hooks/user/CommentHooks/useDeleteReply.ts (1)

3-3: import 경로 업데이트 확인: deleteReply의 상대 경로가 새로운 디렉토리 구조에 맞게 ../../../api/reply.api로 올바르게 수정되었습니다.

src/hooks/user/CommentHooks/usePostComment.ts (1)

2-2: import 경로 업데이트 확인: postComment의 상대 경로가 새로운 디렉토리 구조에 맞게 ../../../api/comment.api로 올바르게 수정되었습니다.

src/hooks/user/useAlarmPatch.ts (2)

2-2: import 경로 업데이트 확인: patchAlarm의 상대 경로가 새로운 디렉토리 구조에 맞게 ../../api/alarm.api로 올바르게 수정되었습니다.


4-4: import 경로 업데이트 확인: useAuthStore의 상대 경로가 새로운 디렉토리 구조에 맞게 ../../store/authStore로 올바르게 수정되었습니다.

src/hooks/user/useChartData.ts (1)

2-2: 임포트 경로 수정 확인.

디렉토리 구조 변경에 따라 import 경로가 ../api/chart.api에서 ../../api/chart.api로 올바르게 수정되었습니다. 코드 기능에는 영향이 없고 경로만 정확하게 변경되었습니다.

src/hooks/user/useGetMyComments.ts (1)

2-3: import 경로가 올바르게、일관성 있게 수정됨.

디렉토리 구조 변경에 따라 activityLog.apiauthStore의 import 경로가 정확하게 수정되었습니다. 두 경로 모두 ../에서 ../../로 변경되어 일관성을 유지하고 있습니다. 기능적 변경 없이 경로만 올바르게 업데이트되었습니다.

src/components/user/manageProjects/passNonPassList/PassNonPassList.tsx (1)

2-4: hooks와 models 임포트 경로가 일관되게 수정됨.

user 디렉토리 구조 변경에 따라 모든 import 경로가 적절하게 수정되었습니다:

  • useMutationParams hook
  • ApplicantInfo 모델
  • ProjectDetailPlusExtended 모델

모든 경로가 일관성 있게 한 단계 더 깊은 경로로 변경되었으며 코드 기능에는 영향이 없습니다.

src/components/user/customerService/notice/NoticeList.tsx (1)

1-2: 고객 서비스 관련 모델 및 유틸리티 임포트 경로 수정 확인.

디렉토리 구조 변경에 따라 다음 항목들의 import 경로가 올바르게 수정되었습니다:

  • NoticeList 타입 임포트 경로
  • formatDate 유틸리티 함수 임포트 경로

두 경로 모두 일관성 있게 한 단계 더 깊은 디렉토리 구조를 반영하도록 변경되었으며, 컴포넌트 로직에는 변화가 없습니다.

src/components/user/customerService/MoveInquiredLink.tsx (1)

2-2: 경로 수정이 올바르게 적용되었습니다.

디렉토리 구조 변경에 따라 ROUTES의 경로가 정확하게 수정되었습니다. 이제 user 디렉토리를 경로에 포함하여 구조가 일관성 있게 유지됩니다.

src/components/user/customerService/noticeDetail/bottom/NoticeDetailBottom.tsx (1)

1-2: 경로 수정이 올바르게 적용되었습니다.

OtherNotice 타입과 ContentBorder 컴포넌트의 import 경로가 새로운 디렉토리 구조에 맞게 적절하게 업데이트되었습니다. 기존보다 더 깊은 디렉토리 구조를 반영하도록 변경되었습니다.

src/components/user/manageProjects/passNonPassList/PassNonPassItem.tsx (1)

1-3: 경로 수정이 올바르게 적용되었습니다.

useMutationParams, ApplicantInfo 및 ProjectDetailPlusExtended의 import 경로가 새로운 디렉토리 구조에 맞게 올바르게 업데이트되었습니다. 이제 모든 user 관련 모듈이 일관된 디렉토리 계층 구조를 따르고 있습니다.

src/components/user/home/projectCardLists/cardList/CardList.tsx (1)

1-1: 경로 수정이 올바르게 적용되었습니다.

PositionButton, Avatar, ProjectList 타입, formatDate 유틸리티의 import 경로가 새로운 디렉토리 구조에 맞게 올바르게 업데이트되었습니다. 상대 경로가 더 깊은 레벨로 조정되어 프로젝트의 새로운 디렉토리 구조를 정확히 반영하고 있습니다.

Also applies to: 4-4, 6-7

src/hooks/user/useGetNotice.ts (1)

2-3: 경로 수정이 올바르게 적용되었습니다.

NoticeSearch 타입과 getNotice 함수의 import 경로가 새로운 디렉토리 구조를 반영하도록 적절히 수정되었습니다. 상대 경로가 ../에서 ../../로 변경되어 user 디렉토리가 추가된 구조를 올바르게 참조하고 있습니다.

src/components/user/home/projectStats/ProjectStats.tsx (1)

1-1: 경로 수정이 올바르게 적용되었습니다.

디렉토리 구조 변경에 따라 import 경로가 수정되었습니다. 기존의 상대 경로가 user 폴더 구조에 맞게 더 깊은 경로로 업데이트되었습니다.

src/components/user/manageProjects/ProjectHeader.tsx (1)

2-3: 경로 수정이 올바르게 적용되었습니다.

컴포넌트의 import 경로가 새로운 디렉토리 구조에 맞게 업데이트되었습니다:

  • Title 컴포넌트: '../common/title/Title''../../common/title/Title'
  • ProjectDetailPlusExtended 타입: '../../models/projectDetail''../../../models/projectDetail'

이러한 변경은 폴더 구조 리팩토링에 필요한 조정이며 코드 기능에는 영향이 없습니다.

src/hooks/user/useApplicantInfo.ts (1)

1-1: 경로 수정이 올바르게 적용되었습니다.

디렉토리 구조 변경에 따른 import 경로가 정확하게 업데이트되었습니다:

  • getApplicantInfo: '../api/applicant.api''../../api/applicant.api'
  • ApiApplicantInfo: '../models/applicant''../../models/applicant'

이러한 변경은 hook이 user 폴더 내에 위치하게 됨에 따라 필요한 조정이며 훅의 기능에는 영향이 없습니다.

Also applies to: 6-6

src/hooks/user/useGetFAQ.ts (2)

2-2: import 경로 업데이트 승인
상위 디렉터리 구조 변경에 맞춰 getFAQ의 import 경로가 올바르게 ../../api/customerService.api로 수정되었습니다.


4-4: import 경로 업데이트 승인
SearchKeyword의 import 경로가 ../../models/customerService로 일관되게 깊어진 구조를 반영하고 있습니다.

src/components/user/manageProjects/CardList.tsx (2)

3-3: import 경로 업데이트 승인
ManagedProject 타입의 import 경로가 ../../../models/manageMyProject로 올바르게 수정되었습니다.


6-6: import 경로 업데이트 승인
ROUTES 상수의 import 경로가 ../../../constants/user/routes로 정확히 반영되었습니다.

src/components/user/comment/CommentLayout.tsx (2)

3-3: import 경로 업데이트 승인
LoadingSpinner의 import 경로가 ../../common/loadingSpinner/LoadingSpinner로 올바르게 깊어진 구조를 따르고 있습니다.


4-4: import 경로 업데이트 승인
useGetComment 훅의 import 경로가 ../../../hooks/user/CommentHooks/useGetComment로 정확히 수정되었습니다.

src/components/user/customerService/noticeDetail/bottom/button/ListButton.tsx (2)

1-1: import 경로 업데이트 승인
ROUTES의 import 경로가 ../../../../../../constants/user/routes로 일관성 있게 조정되었습니다.


2-2: import 경로 업데이트 승인
ContentBorder의 import 경로가 ../../../../../common/contentBorder/ContentBorder로 정확히 반영되었습니다.

src/components/user/home/searchFiltering/filteringContents/FilteringContents.tsx (1)

5-10: import 경로가 올바르게 업데이트되었습니다.

모든 import 경로가 새 디렉터리 구조에 맞게 정확히 수정되었습니다. 이 변경 사항은 컴포넌트의 기능에 영향을 주지 않으면서 일관된 파일 구조를 유지합니다.

src/components/user/comment/replyComponent/ReplyComponent.tsx (1)

1-12: import 경로가 올바르게 업데이트되었습니다.

모든 import 경로가 새 디렉터리 구조에 맞게 정확히 수정되었습니다. Avatar, useComment, DropDown, useGetReply, LoadingSpinner, ROUTES 등의 모든 경로가 user 폴더를 포함하도록 일관성 있게 업데이트되었습니다.

src/components/user/comment/commentComponent/CommentComponentLayout.tsx (1)

2-6: import 경로가 올바르게 업데이트되었습니다.

DropDown, CommentType, useComment 등 모든 import 경로가 새 디렉터리 구조에 맞게 정확히 수정되었습니다. 이 변경 사항으로 일관된 파일 구조를 유지하면서도 컴포넌트의 기능에는 영향을 주지 않습니다.

src/components/user/comment/commentInput/CommentInput.tsx (1)

3-12: import 경로가 올바르게 업데이트되었습니다.

모든 import 경로가 새 디렉터리 구조에 맞게 정확히 수정되었습니다. useMyProfileInfo, formatImgPath, Avatar, useInputFocus, 그리고 모든 Comment 관련 hooks의 경로가 user 폴더를 포함하도록 일관성 있게 업데이트되었습니다.

src/components/user/customerService/inquiry/Inquiry.tsx (1)

6-6: import 경로가 올바르게 수정되었습니다.

디렉토리 구조 변경에 따라 import 경로가 적절하게 업데이트되었습니다. user/ 디렉토리가 추가되면서 경로의 깊이가 조정되었고, 모든 모듈이 올바른 위치에서 가져와집니다.

Also applies to: 10-11, 13-14

src/components/user/home/projectCardLists/ProjectCardLists.tsx (1)

2-2: import 경로가 올바르게 수정되었습니다.

디렉토리 구조 변경에 따라 import 경로가 적절하게 업데이트되었습니다. 모든 경로는 새로운 디렉토리 구조를 올바르게 반영하고 있습니다:

  1. 훅(useProjectCardListData, useSaveSearchFiltering)에 user/ 디렉토리가 추가됨
  2. 상수(ROUTES)에 user/ 디렉토리가 추가됨
  3. 공통 컴포넌트(EmptyLoading, NoResult, Pagination)의 경로가 적절하게 조정됨

컴포넌트의 기능이나 로직에는 변경이 없으며, 경로 수정만 이루어졌습니다.

Also applies to: 6-10

src/routes/AppRoutes.tsx (2)

15-15: ROUTES 상수의 import 경로가 올바르게 수정되었습니다.

디렉토리 구조 변경에 따라 ROUTES 상수의 import 경로가 ../constants/user/routes로 적절하게 업데이트되었습니다.


18-101: 지연 로딩 컴포넌트들의 import 경로가 올바르게 수정되었습니다.

모든 지연 로딩(lazy loading) 컴포넌트들의 import 경로가 디렉토리 구조 변경에 맞게 적절하게 업데이트되었습니다. 주요 변경 사항:

  1. 사용자 관련 페이지들이 ../pages/user/ 경로로 이동됨
  2. 사용자 관련 컴포넌트들이 ../components/user/ 경로로 이동됨
  3. 중첩된 컴포넌트 경로들도 일관되게 수정됨

라우팅 로직이나 컴포넌트 사용 방식에는 변경이 없고, 경로 수정만 이루어졌습니다.

src/components/user/evaluation/EvaluationContent.tsx (1)

2-5: import 경로가 새 구조에 맞게 올바르게 수정됨
useEvaluationStep, MemberList, optionLabels, questions의 import 경로가 user 디렉토리를 포함하도록 업데이트되었습니다. 로직에는 영향이 없으며, 경로 수정이 적절합니다.

Comment on lines 5 to 8
<<<<<<< HEAD
=======

>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

병합 충돌 마커(<<<<<<<, =======, >>>>>>>) 제거 필요
현재 import 섹션에 Git 충돌 마커가 남아 있어 파싱 오류 및 빌드 실패를 유발합니다. Biome 정적 분석 오류(numbers cannot be followed by identifiers directly after)도 이로 인해 발생합니다.
충돌 마커를 제거하고, 의도된 import 경로만 남겨주세요.

-<<<<<<< HEAD
-=======
->>>>>>> 4069f4a (chore: 디렉토리 변경에 따른  경로수정)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<<<<<<< HEAD
=======
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
🧰 Tools
🪛 Biome (1.9.4)

[error] 8-8: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

🤖 Prompt for AI Agents
In src/hooks/user/ProjectHooks/useTagSelectors.ts around lines 5 to 8, there are
leftover Git merge conflict markers (<<<<<<<, =======, >>>>>>>) in the import
section causing parsing errors and build failures. Remove all these conflict
markers and keep only the intended import statements with correct paths to
resolve the issue.

Comment on lines 3 to 16
<<<<<<< HEAD
import { managedProjectKey } from '../../queries/user/keys';
import { putProject } from '../../../api/joinProject.api';
import { MODAL_MESSAGE } from '../../../constants/user/modalMessage';
import { FormData } from '../../../models/createProject';
import { ROUTES } from '../../../constants/user/routes';
=======
import { putProject } from '../../../api/joinProject.api';
import { managedProjectKey } from '../../queries/user/keys';
import { FormData } from '../../../models/createProject';
import { MODAL_MESSAGE } from '../../../constants/user/modalMessage';
import { ROUTES } from '../../../constants/user/routes';

>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

병합 충돌 마커 제거 필요: <<<<<<< HEAD, =======, >>>>>>> 4069f4a 충돌 마커가 남아 있어 컴파일 에러를 초래합니다. 중복된 import 구문과 마커를 모두 제거하고, 필요한 import만 남겨주세요.

🧰 Tools
🪛 Biome (1.9.4)

[error] 8-9: Expected a statement but instead found '======='.

Expected a statement here.

(parse)


[error] 16-16: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)


[error] 10-10: Shouldn't redeclare 'putProject'. Consider to delete it or rename it.

'putProject' is defined here:

(lint/suspicious/noRedeclare)


[error] 11-11: Shouldn't redeclare 'managedProjectKey'. Consider to delete it or rename it.

'managedProjectKey' is defined here:

(lint/suspicious/noRedeclare)


[error] 12-12: Shouldn't redeclare 'FormData'. Consider to delete it or rename it.

'FormData' is defined here:

(lint/suspicious/noRedeclare)


[error] 13-13: Shouldn't redeclare 'MODAL_MESSAGE'. Consider to delete it or rename it.

'MODAL_MESSAGE' is defined here:

(lint/suspicious/noRedeclare)


[error] 14-14: Shouldn't redeclare 'ROUTES'. Consider to delete it or rename it.

'ROUTES' is defined here:

(lint/suspicious/noRedeclare)

🤖 Prompt for AI Agents
In src/hooks/user/ProjectHooks/useUpdateProject.ts between lines 3 and 16,
remove the merge conflict markers <<<<<<< HEAD, =======, and >>>>>>> 4069f4a
along with any duplicated import statements. Keep only one set of necessary
imports to ensure the file compiles without errors.

Comment on lines 2 to 5
<<<<<<< HEAD
=======
import { ApplySchemeType } from '../../../../pages/user/apply/Apply';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

병합 충돌 마커가 남아있습니다.

코드에 병합 충돌 마커(<<<<<<< HEAD, =======, >>>>>>> 4069f4a)가 남아있습니다. 이로 인해 코드가 실행되지 않을 수 있습니다. 병합 충돌을 해결하고 적절한 import 경로를 선택해야 합니다.

다음과 같이 수정해주세요:

-<<<<<<< HEAD
-=======
-import { ApplySchemeType } from '../../../../pages/user/apply/Apply';
->>>>>>> 4069f4a (chore: 디렉토리 변경에 따른  경로수정)
+import { ApplySchemeType } from '../../../../pages/user/apply/Apply';
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<<<<<<< HEAD
=======
import { ApplySchemeType } from '../../../../pages/user/apply/Apply';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
import { ApplySchemeType } from '../../../../pages/user/apply/Apply';
🧰 Tools
🪛 Biome (1.9.4)

[error] 5-5: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

🤖 Prompt for AI Agents
In src/components/user/applyComponents/phoneComponent/PhoneComponent.tsx around
lines 2 to 5, there are leftover merge conflict markers (<<<<<<< HEAD, =======,
>>>>>>> 4069f4a) that must be removed. Resolve the conflict by deleting these
markers and keeping the correct import statement for ApplySchemeType from
'../../../../pages/user/apply/Apply'. Ensure the file contains only valid import
statements without any conflict markers.

Comment on lines 2 to 10
<<<<<<< HEAD
import { ProjectListKey, userInfoKey } from '../../queries/user/keys';
=======
import { joinProject } from '../../../models/joinProject';
import { ProjectListKey, userInfoKey } from '../../queries/user/keys';
import { postApplicantProject } from '../../../api/joinProject.api';
import { MODAL_MESSAGE } from '../../../constants/user/modalMessage';
import { ROUTES } from '../../../constants/user/routes';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

병합 충돌을 해결해야 합니다.

파일에 병합 충돌 마커(<<<<<<< HEAD, =======, >>>>>>> 4069f4a)가 남아있습니다. 이로 인해 중복된 import 문이 있으며 코드 실행 시 오류가 발생할 수 있습니다.

다음과 같이 병합 충돌을 해결하세요:

-<<<<<<< HEAD
-import { ProjectListKey, userInfoKey } from '../../queries/user/keys';
-=======
-import { joinProject } from '../../../models/joinProject';
-import { ProjectListKey, userInfoKey } from '../../queries/user/keys';
-import { postApplicantProject } from '../../../api/joinProject.api';
-import { MODAL_MESSAGE } from '../../../constants/user/modalMessage';
-import { ROUTES } from '../../../constants/user/routes';
->>>>>>> 4069f4a (chore: 디렉토리 변경에 따른  경로수정)
+import { ProjectListKey, userInfoKey } from '../../queries/user/keys';
+import { joinProject } from '../../../models/joinProject';
+import { postApplicantProject } from '../../../api/joinProject.api';
+import { MODAL_MESSAGE } from '../../../constants/user/modalMessage';
+import { ROUTES } from '../../../constants/user/routes';

파일 하단에 중복된 import 문이 이미 있으므로 충돌 부분을 완전히 제거하고 중복되지 않은 ProjectListKeyuserInfoKey import만 유지하는 것이 좋습니다.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<<<<<<< HEAD
import { ProjectListKey, userInfoKey } from '../../queries/user/keys';
=======
import { joinProject } from '../../../models/joinProject';
import { ProjectListKey, userInfoKey } from '../../queries/user/keys';
import { postApplicantProject } from '../../../api/joinProject.api';
import { MODAL_MESSAGE } from '../../../constants/user/modalMessage';
import { ROUTES } from '../../../constants/user/routes';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
import { ProjectListKey, userInfoKey } from '../../queries/user/keys';
import { joinProject } from '../../../models/joinProject';
import { postApplicantProject } from '../../../api/joinProject.api';
import { MODAL_MESSAGE } from '../../../constants/user/modalMessage';
import { ROUTES } from '../../../constants/user/routes';
🧰 Tools
🪛 Biome (1.9.4)

[error] 3-4: Expected a statement but instead found '======='.

Expected a statement here.

(parse)


[error] 10-10: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)


[error] 6-6: Shouldn't redeclare 'ProjectListKey'. Consider to delete it or rename it.

'ProjectListKey' is defined here:

(lint/suspicious/noRedeclare)


[error] 6-6: Shouldn't redeclare 'userInfoKey'. Consider to delete it or rename it.

'userInfoKey' is defined here:

(lint/suspicious/noRedeclare)

🤖 Prompt for AI Agents
In src/hooks/user/ProjectHooks/useApplyProject.ts between lines 2 and 10, there
are leftover merge conflict markers causing duplicate imports and potential
runtime errors. Remove all conflict markers (<<<<<<< HEAD, =======, >>>>>>>
4069f4a) and ensure only one set of unique import statements remains, keeping
the imports for ProjectListKey and userInfoKey without duplication.

Comment on lines 2 to 6
<<<<<<< HEAD
=======
import { MemberList } from '../../../models/evaluation';
import { questions } from '../../../constants/user/evaluation';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

⚠️ Potential issue

병합 충돌 마커 제거 및 중복 import 정리
<<<<<<<, =======, >>>>>>> 병합 충돌 마커가 남아 있고, 중복된 MemberListquestions import가 생성되었습니다. 이로 인해 문법 오류와 불필요한 중복이 발생합니다.
아래와 같이 충돌 마커와 중복 import를 제거해주세요:

- <<<<<<< HEAD
- =======
- >>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
- import { MemberList } from '../../../models/evaluation';
- import { questions } from '../../../constants/user/evaluation';
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<<<<<<< HEAD
=======
import { MemberList } from '../../../models/evaluation';
import { questions } from '../../../constants/user/evaluation';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
🧰 Tools
🪛 Biome (1.9.4)

[error] 6-6: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

🤖 Prompt for AI Agents
In src/hooks/user/evaluationHooks/useEvaluationStep.ts between lines 2 and 6,
remove the Git merge conflict markers <<<<<<<, =======, and >>>>>>> along with
any duplicated imports of MemberList and questions. Keep only one clean set of
necessary imports to fix syntax errors and avoid redundancy.

Comment on lines 2 to 10
<<<<<<< HEAD
import { ProjectMemberListEval } from '../../queries/user/keys';
import { apiEvaluatedUser } from '../../../models/evaluation';
import { postEvaluation } from '../../../api/evaluation.api';
=======
import { postEvaluation } from '../../../api/evaluation.api';
import { ProjectMemberListEval } from '../../queries/user/keys';
import { apiEvaluatedUser } from '../../../models/evaluation';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

⚠️ Potential issue

병합 충돌 마커 제거 및 import 정리
병합 충돌 마커(<<<<<<<, =======, >>>>>>>)와 중복 import가 남아 있습니다. 코드 파싱 오류를 방지하기 위해 아래와 같이 정리해주세요:

- <<<<<<< HEAD
- import { ProjectMemberListEval } from '../../queries/user/keys';
- import { apiEvaluatedUser } from '../../../models/evaluation';
- import { postEvaluation } from '../../../api/evaluation.api';
- =======
- import { postEvaluation } from '../../../api/evaluation.api';
- import { ProjectMemberListEval } from '../../queries/user/keys';
- import { apiEvaluatedUser } from '../../../models/evaluation';
- >>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
+ import { postEvaluation } from '../../../api/evaluation.api';
+ import { ProjectMemberListEval } from '../../queries/user/keys';
+ import { apiEvaluatedUser } from '../../../models/evaluation';
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<<<<<<< HEAD
import { ProjectMemberListEval } from '../../queries/user/keys';
import { apiEvaluatedUser } from '../../../models/evaluation';
import { postEvaluation } from '../../../api/evaluation.api';
=======
import { postEvaluation } from '../../../api/evaluation.api';
import { ProjectMemberListEval } from '../../queries/user/keys';
import { apiEvaluatedUser } from '../../../models/evaluation';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
import { postEvaluation } from '../../../api/evaluation.api';
import { ProjectMemberListEval } from '../../queries/user/keys';
import { apiEvaluatedUser } from '../../../models/evaluation';
🧰 Tools
🪛 Biome (1.9.4)

[error] 5-6: Expected a statement but instead found '======='.

Expected a statement here.

(parse)


[error] 10-10: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)


[error] 7-7: Shouldn't redeclare 'postEvaluation'. Consider to delete it or rename it.

'postEvaluation' is defined here:

(lint/suspicious/noRedeclare)


[error] 8-8: Shouldn't redeclare 'ProjectMemberListEval'. Consider to delete it or rename it.

'ProjectMemberListEval' is defined here:

(lint/suspicious/noRedeclare)


[error] 9-9: Shouldn't redeclare 'apiEvaluatedUser'. Consider to delete it or rename it.

'apiEvaluatedUser' is defined here:

(lint/suspicious/noRedeclare)

🤖 Prompt for AI Agents
In src/hooks/user/evaluationHooks/usePostEvaluation.ts around lines 2 to 10,
remove the merge conflict markers <<<<<<<, =======, and >>>>>>> along with any
duplicate imports. Ensure the import statements are clean, correctly ordered,
and without repetition to prevent parsing errors.

Comment on lines 2 to 6
<<<<<<< HEAD
=======
import { getEvaluation } from '../../../api/evaluation.api';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
import { ProjectMemberListEval } from '../../queries/user/keys';
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

⚠️ Potential issue

병합 충돌 마커 제거 및 중복 import 정리
<<<<<<<, =======, >>>>>>> 병합 충돌 마커가 남아 있으며, getEvaluation이 중복 import 되었습니다. 문법 오류를 방지하도록 아래와 같이 정리해주세요:

- <<<<<<< HEAD
- =======
- import { getEvaluation } from '../../../api/evaluation.api';
- >>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
- import { getEvaluation } from '../../../api/evaluation.api';  // 중복된 import
+ import { getEvaluation } from '../../../api/evaluation.api';
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<<<<<<< HEAD
=======
import { getEvaluation } from '../../../api/evaluation.api';
>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)
import { ProjectMemberListEval } from '../../queries/user/keys';
import { getEvaluation } from '../../../api/evaluation.api';
import { ProjectMemberListEval } from '../../queries/user/keys';
🧰 Tools
🪛 Biome (1.9.4)

[error] 4-6: Expected a statement but instead found '>>>>>>> 4069f4a (chore: 디렉토리 변경에 따른 경로수정)'.

Expected a statement here.

(parse)


[error] 5-5: numbers cannot be followed by identifiers directly after

an identifier cannot appear here

(parse)

🤖 Prompt for AI Agents
In src/hooks/user/evaluationHooks/useGetEvaluation.ts around lines 2 to 6,
remove the merge conflict markers <<<<<<<, =======, and >>>>>>> and eliminate
the duplicate import of getEvaluation. Ensure only one clean import statement
for getEvaluation remains without any conflict markers to fix the syntax errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🛠개선 성능 개선/리팩토링에 대한 라벨

Projects

None yet

Development

Successfully merging this pull request may close these issues.

관리자 페이지를 위한 경로 세팅

3 participants