chore : 문제 검색 api 경로 변경

[chat26666]

PR 생성 시 아래 항목을 채워주세요.

제목 예시: feat : Pull request template 작성

(작성 후 이 안내 문구는 삭제해주세요)

---

작업 내용

• api 경로를 /api/problems/search && /api/problems/suggestions 로 변경하였습니다.

---

Summary by CodeRabbit

• Refactor
  • 검색 관련 API 엔드포인트가 /api/problems 경로로 변경되었습니다.
  • 검색 페이지에서 사용되는 검색 및 추천 요청 URL이 새로운 엔드포인트에 맞게 수정되었습니다.
  • 기존 기능에는 영향이 없으며, 사용자는 변경된 경로를 통해 동일하게 검색 기능을 이용할 수 있습니다.

[coderabbitai]

Walkthrough

이 변경사항은 문제 검색 컨트롤러의 패키지와 엔드포인트 경로를 수정하고, 프론트엔드 검색 페이지에서 관련 API 호출 경로를 새로운 엔드포인트에 맞게 업데이트합니다. 메서드 시그니처나 로직에는 변동이 없습니다.

Changes

파일/경로	변경 요약
.../presentation/problemmanagement/problem/ProblemSearchController.java	패키지 변경, 클래스 및 메서드의 RequestMapping 경로 수정
.../resources/templates/search-page.html	JS fetch 요청의 API 엔드포인트 경로를 새로운 경로로 변경

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant SearchPage (Frontend)
    participant ProblemSearchController (Backend)

    User->>SearchPage: 검색어 입력
    SearchPage->>ProblemSearchController: GET /api/problems/suggestions (Authorization)
    ProblemSearchController-->>SearchPage: 검색 제안 반환

    User->>SearchPage: 검색 실행
    SearchPage->>ProblemSearchController: GET /api/problems/search (Authorization)
    ProblemSearchController-->>SearchPage: 검색 결과 반환

Loading

Possibly related PRs

• feat : 문제 검색엔진추가(elasticsearch) 검색 자동 완성 기능 추가 #32: ProblemSearchController 클래스 및 검색 엔드포인트 도입과 관련된 PR로, 이번 변경의 컨트롤러 및 엔드포인트 수정과 직접적으로 연결됩니다.

Poem

🐇
API 경로가 새롭게 바뀌었지,
"/api/problems"로 토끼가 뛰었지!
검색 제안도, 결과도 척척,
프론트엔드와 백엔드가 찰떡!
오늘도 코드는 깔끔하게,
토끼는 당근 한 입에! 🥕

---

📜 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 4caaf35 and ed0a617.

📒 Files selected for processing (2)

• src/main/java/org/ezcode/codetest/presentation/problemmanagement/problem/ProblemSearchController.java (3 hunks)
• src/main/resources/templates/search-page.html (2 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: chat26666
PR: ezcode-my/backend#37
File: src/main/java/org/ezcode/codetest/infrastructure/elasticsearch/repository/ProblemElasticsearchRepositoryDsl.java:10-10
Timestamp: 2025-06-06T19:56:27.759Z
Learning: When user chat26666 mentions that code was implemented in a previous PR but explanation was missing, they may submit a follow-up PR just to add documentation/explanation without the actual implementation code.

src/main/resources/templates/search-page.html (1)

Learnt from: chat26666
PR: ezcode-my/backend#31
File: src/main/resources/templates/search-page.html:198-233
Timestamp: 2025-06-04T15:14:15.092Z
Learning: src/main/resources/templates/search-page.html은 임시용 뷰로, 곧 폐기될 예정임

src/main/java/org/ezcode/codetest/presentation/problemmanagement/problem/ProblemSearchController.java (2)

Learnt from: Kimminu7
PR: ezcode-my/backend#63
File: src/main/java/org/ezcode/codetest/infrastructure/persistence/repository/problem/ProblemQueryRepositoryImpl.java:24-40
Timestamp: 2025-06-14T14:33:58.372Z
Learning: ProblemController에서 ProblemSearchCondition 객체는 항상 new ProblemSearchCondition(category, difficulty)로 유효한 인스턴스를 생성해서 전달하므로, ProblemQueryRepositoryImpl의 searchByCondition 메서드에서 searchCondition 파라미터 자체에 대한 null 체크는 불필요하다. category와 difficulty 필드만 각각 null일 수 있다.

Learnt from: chat26666
PR: ezcode-my/backend#31
File: src/main/java/org/ezcode/codetest/domain/problem/model/entity/ProblemSearchDocument.java:49-56
Timestamp: 2025-06-05T00:52:54.460Z
Learning: ProblemSearchDocument.from() 메서드는 트랜잭션 내에서 DB에서 실제로 조회한 Problem 엔티티만 사용하므로 null 체크가 불필요함. 이 컨텍스트에서는 null Problem이 있을 경우 이미 이전 단계에서 예외가 발생함.

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build

🔇 Additional comments (5)

src/main/java/org/ezcode/codetest/presentation/problemmanagement/problem/ProblemSearchController.java (3)

1-1: 패키지 구조 개선이 적절합니다.

문제 관련 컨트롤러를 별도 하위 패키지로 분리한 것은 좋은 구조적 개선입니다.

---

25-25: API 경로 표준화가 잘 적용되었습니다.

/api 접두사를 추가하여 REST API 규칙을 따른 것이 좋습니다.

---

54-54: 기존 API 호출 경로 업데이트 완료

모든 /problems/search 호출이 /api/problems/search로 변경된 것을 확인했습니다.

• src/main/resources/templates/search-page.html:208행에서 /api/problems/search?keyword=로 적절히 호출되고 있습니다.

더 이상 업데이트되지 않은 경로가 없습니다. 🚀

src/main/resources/templates/search-page.html (2)

136-136: 백엔드 API 변경에 맞춰 제안 엔드포인트가 올바르게 업데이트되었습니다.

/api/problems/suggestions 경로가 새로운 컨트롤러 매핑과 일치합니다.

---

208-208: 백엔드 API 변경에 맞춰 검색 엔드포인트가 올바르게 업데이트되었습니다.

/api/problems/search 경로가 새로운 컨트롤러 매핑과 일치합니다.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.