Skip to content

Comments

feat: paginate /characters#29

Open
sleegme wants to merge 1 commit intodevfrom
feat/characters-pagination
Open

feat: paginate /characters#29
sleegme wants to merge 1 commit intodevfrom
feat/characters-pagination

Conversation

@sleegme
Copy link
Collaborator

@sleegme sleegme commented Feb 20, 2026

##📋 작업 내용
-Controller
GET /api/v1/characters에 page, limit Query 파라미터 추가
응답 모델을 list[CharacterResponse] → CharacterPageResponse로 변경
character_service.get_characters(db, page, limit) 호출하도록 수정

-Service
get_characters(db, page, limit) 신규 추가
offset 계산 후 Repository 호출
total count 조회 로직 추가

-Repository
count(db) 메서드 신규 추가
기존 get_all(db, skip, limit) 재사용

-Schema
CharacterPageResponse(items, total, page, limit) 신규 추가
기존 스키마 변경 없음

🎯 관련 이슈
Closes #이슈번호

🤖 사용한 Prompt
없음

🔌 API 변경사항
수정 엔드포인트
GET /api/v1/characters
요청 변경사항
Query 파라미터 page, limit 추가
응답 변경사항
배열 → 객체 래핑 형태로 변경
하위 호환성 영향
클라이언트에서 items 기준으로 접근 필요
💾 데이터/인프라 변경사항
DB 모델 변경 없음
마이그레이션 없음
환경 변수 변경 없음

@gemini-code-assist
Copy link

Summary of Changes

Hello @sleegme, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

이 PR은 /api/v1/characters 엔드포인트에 페이지네이션 기능을 구현하여 대량의 캐릭터 데이터를 효율적으로 처리하고 클라이언트가 필요한 만큼의 데이터만 요청할 수 있도록 개선합니다. 이를 통해 API의 확장성과 성능이 향상되며, 사용자 경험이 개선될 것으로 기대됩니다.

Highlights

  • API Pagination: /api/v1/characters 엔드포인트에 pagelimit 쿼리 파라미터가 추가되어 캐릭터 목록을 페이지별로 조회할 수 있도록 페이지네이션 기능이 구현되었습니다.
  • Response Model Change: /characters 엔드포인트의 응답 모델이 list[CharacterResponse]에서 CharacterPageResponse 객체로 변경되어, 전체 항목 수, 현재 페이지, 제한 정보를 포함하는 구조로 제공됩니다.
  • Total Count Functionality: character_repo.pycount 메서드가 새로 추가되어 전체 캐릭터 수를 효율적으로 조회할 수 있는 기능이 도입되었습니다.
  • Service Layer Pagination Logic: character_service.pyget_characters 함수가 추가되어 페이지네이션 로직을 처리하고, 기존 리포지토리의 get_all 메서드를 재사용하여 데이터를 가져옵니다.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • .gitignore
    • maplewind.db 파일이 Git 추적에서 제외되도록 추가되었습니다.
  • controller/v1/characters.py
    • /characters 엔드포인트에 pagelimit 쿼리 파라미터가 추가되었고, 응답 모델이 CharacterPageResponse로 변경되었습니다.
  • repositories/character_repo.py
    • 전체 캐릭터 수를 조회하는 count 메서드가 추가되었습니다.
  • schemas/character_dto.py
    • 페이지네이션 정보를 포함하는 CharacterPageResponse 스키마가 새로 정의되었습니다.
  • services/character_service.py
    • 페이지네이션 로직을 구현하는 get_characters 서비스 함수가 추가되었습니다.
Activity
  • 현재까지 이 PR에 대한 추가적인 활동 (댓글, 리뷰 등)은 없습니다.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 20, 2026

📝 Walkthrough

Summary by CodeRabbit

릴리즈 노트

  • 새로운 기능
    • 캐릭터 목록 조회에 페이지네이션 기능이 추가되었습니다. 사용자는 이제 페이지 번호와 페이지당 항목 수를 지정하여 캐릭터를 조회할 수 있으며, 최대 100개 항목까지 한 번에 조회할 수 있습니다.

요약

캐릭터 조회 엔드포인트에 페이지네이션 기능을 추가했습니다. 컨트롤러에 page와 limit 쿼리 파라미터를 도입하고, 새로운 CharacterPageResponse DTO를 정의하며, 저장소에 count() 함수를, 서비스에 페이지네이션 로직을 구현했습니다.

변경 사항

코호트 / 파일 요약
페이지네이션 DTO
schemas/character_dto.py
캐릭터 페이지 응답 데이터를 위한 새로운 CharacterPageResponse 클래스 추가 (items, total, page, limit 필드 포함)
저장소 계층
repositories/character_repo.py
캐릭터 전체 개수를 조회하는 count() 함수 추가
서비스 계층
services/character_service.py
페이지네이션을 지원하는 get_characters() 함수 추가 (offset 계산, 저장소 호출, 전체 개수 조회)
컨트롤러 계층
controller/v1/characters.py
get_characters 엔드포인트에 page, limit 쿼리 파라미터 추가, CharacterPageResponse 응답 모델로 변경, 새로운 import 추가
설정 파일
.gitignore
maplewind.db 엔트리 중복 추가

시퀀스 다이어그램

sequenceDiagram
    participant Client
    participant Controller as Controller<br/>(characters.py)
    participant Service as Service<br/>(character_service.py)
    participant Repository as Repository<br/>(character_repo.py)
    participant Database

    Client->>Controller: GET /characters?page=1&limit=10
    Controller->>Service: get_characters(db, page=1, limit=10)
    Service->>Repository: get_all(db, skip=0, limit=10)
    Repository->>Database: SELECT * FROM character LIMIT 10 OFFSET 0
    Database-->>Repository: 캐릭터 데이터
    Repository-->>Service: [캐릭터 목록]
    Service->>Repository: count(db)
    Repository->>Database: SELECT COUNT(Character.id)
    Database-->>Repository: 전체 개수
    Repository-->>Service: 총 개수
    Service-->>Controller: {items: [...], total: N, page: 1, limit: 10}
    Controller-->>Client: CharacterPageResponse
Loading

코드 리뷰 예상 난이도

🎯 3 (중간) | ⏱️ ~25분

🐰 페이지네이션을 심는 토끼,
페이지와 리미트로 정원을 나누고,
저장소의 count로 꽃의 개수를 센다.
서비스의 손길 거쳐
완벽한 구획으로 정렬되네! 🌷✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed 제목 'feat: paginate /characters'는 PR의 주요 변경 사항인 /characters 엔드포인트에 페이지네이션을 추가하는 것을 명확하게 나타냅니다.
Description check ✅ Passed 설명은 Controller, Service, Repository, Schema 변경 사항과 API 변경 내용을 자세히 포함하고 있어 변경 사항과 관련이 있습니다.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/characters-pagination

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request introduces pagination to the /characters endpoint, which is a good improvement for handling large datasets. The changes involve modifying the controller to accept page and limit query parameters, updating the service layer to calculate offset and retrieve paginated data, and adding a count method to the repository. A new CharacterPageResponse schema is also introduced to wrap the paginated results. The .gitignore file was also updated, but it seems to have a duplicate entry for maplewind.db.

async def get_characters(db: AsyncSession, page: int, limit: int):
offset = (page - 1) * limit

# 기존 repo의 get_all을 그대로 재사용 (리스크 최소)

Choose a reason for hiding this comment

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

medium

The comment 기존 repo의 get_all을 그대로 재사용 (리스크 최소) is not necessary. The code is self-explanatory.

Suggested change
# 기존 repo의 get_all을 그대로 재사용 (리스크 최소)
items = await character_repo.get_all(db, skip=offset, limit=limit)

Copy link
Contributor

@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: 6

🧹 Nitpick comments (1)
services/character_service.py (1)

19-31: CharacterPageResponse를 직접 반환하는 방식 권장

현재 dict를 반환하면 FastAPI가 response_model을 통해 CharacterPageResponse로 변환하지만, 서비스 레이어에서 직접 DTO를 생성하면 타입 안전성이 높아지고 서비스 계약이 더 명확해집니다.

♻️ 리팩터링 제안

services/character_service.py 상단에 import 추가:

from schemas.character_dto import CharacterPageResponse

함수 본문 변경:

-async def get_characters(db: AsyncSession, page: int, limit: int):
+async def get_characters(db: AsyncSession, page: int, limit: int) -> CharacterPageResponse:
     offset = (page - 1) * limit
     items = await character_repo.get_all(db, skip=offset, limit=limit)
     total = await character_repo.count(db)
-    return {
-        "items": items,
-        "total": total,
-        "page": page,
-        "limit": limit,
-    }
+    return CharacterPageResponse(items=items, total=total, page=page, limit=limit)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@services/character_service.py` around lines 19 - 31, get_characters currently
returns a plain dict which loses type safety; change it to construct and return
a CharacterPageResponse DTO instead: import CharacterPageResponse from
schemas.character_dto at the top, then inside get_characters (the async function
using db: AsyncSession, page, limit and character_repo.get_all /
character_repo.count) create and return a CharacterPageResponse(...) instance
populated with items, total, page and limit so the service layer returns the
explicit DTO rather than a raw dict.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.gitignore:
- Around line 11-12: Remove the duplicate entry "maplewind.db" from .gitignore
so the file only lists it once; locate the two consecutive "maplewind.db" lines
and delete the redundant line, leaving a single occurrence.

In `@controller/v1/characters.py`:
- Line 15: Update the pagination default for the query param currently declared
as "limit: int = Query(10, ge=1, le=100)" in controller/v1/characters.py to use
the guideline default of 20 (i.e., change the Query default from 10 to 20) while
keeping the existing type and constraints (ge=1, le=100); ensure the endpoint's
pagination signature aligns with the convention "page: int = 1, limit: int = 20"
if the page param exists in the same function.
- Line 16: The ruff B008 warning flags the use of the FastAPI dependency pattern
Depends(get_db) even though it's an approved project convention; fix by either
adding "B008" to the ignore list in ruff.toml or by appending a per-line
suppression comment to the dependency declaration (e.g., add "# noqa: B008" to
the line containing Depends(get_db)), ensuring the symbol Depends(get_db)
remains unchanged.

In `@schemas/character_dto.py`:
- Line 1: Remove the import of typing.List and replace any uses of List[...]
with the native Python 3.12 generic builtin list[...] (e.g., change
List[CharacterResponse] to list[CharacterResponse]); update imports in
schemas/character_dto.py to drop "from typing import List" and ensure any
function signatures, class attributes, or type hints (e.g., CharacterResponse,
CharacterDTO, or variables currently annotated with List[...]) use the new
list[...] syntax consistently.

In `@services/character_service.py`:
- Line 22: Remove the unnecessary self-explanatory inline comment "# 기존 repo의
get_all을 그대로 재사용 (리스크 최소)" in services/character_service.py; locate the place
where get_all is reused (the call or wrapper named get_all) and delete that
comment line so the code remains clean and follows the "no comments for obvious
code" guideline.
- Line 19: The function get_characters is missing a return type annotation;
update its signature (async def get_characters(db: AsyncSession, page: int,
limit: int) -> ...) to include the correct return type—either a paginated
response type like CharacterPageResponse or a more explicit collection type
(e.g., List[Character] / Sequence[Character]) depending on what the function
actually returns; ensure imports for CharacterPageResponse or typing types are
added and adjust any internal returns to match the declared type.

---

Nitpick comments:
In `@services/character_service.py`:
- Around line 19-31: get_characters currently returns a plain dict which loses
type safety; change it to construct and return a CharacterPageResponse DTO
instead: import CharacterPageResponse from schemas.character_dto at the top,
then inside get_characters (the async function using db: AsyncSession, page,
limit and character_repo.get_all / character_repo.count) create and return a
CharacterPageResponse(...) instance populated with items, total, page and limit
so the service layer returns the explicit DTO rather than a raw dict.

Comment on lines +11 to +12
maplewind.db
maplewind.db
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

중복된 .gitignore 항목 제거 필요

maplewind.db가 연속으로 두 번 추가되었습니다. 동작에는 영향 없지만 하나를 삭제해야 합니다.

🔧 수정 제안
 # Virtual environments
 .venv
 maplewind.db
-maplewind.db
📝 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
maplewind.db
maplewind.db
# Virtual environments
.venv
maplewind.db
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.gitignore around lines 11 - 12, Remove the duplicate entry "maplewind.db"
from .gitignore so the file only lists it once; locate the two consecutive
"maplewind.db" lines and delete the redundant line, leaving a single occurrence.

@router.get("", response_model=CharacterPageResponse)
async def get_characters(
page: int = Query(1, ge=1),
limit: int = Query(10, ge=1, le=100),
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

limit 기본값 불일치 — 20이어야 합니다

가이드라인에서 페이지네이션은 page: int = 1, limit: int = 20으로 구현해야 한다고 명시되어 있습니다. 현재 기본값이 10입니다.

🔧 수정 제안
-    limit: int = Query(10, ge=1, le=100),
+    limit: int = Query(20, ge=1, le=100),

Based on learnings: "Applies to controller/v1/*.py: Pagination should be implemented via query parameters: page: int = 1, limit: int = 20."

📝 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
limit: int = Query(10, ge=1, le=100),
limit: int = Query(20, ge=1, le=100),
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@controller/v1/characters.py` at line 15, Update the pagination default for
the query param currently declared as "limit: int = Query(10, ge=1, le=100)" in
controller/v1/characters.py to use the guideline default of 20 (i.e., change the
Query default from 10 to 20) while keeping the existing type and constraints
(ge=1, le=100); ensure the endpoint's pagination signature aligns with the
convention "page: int = 1, limit: int = 20" if the page param exists in the same
function.

async def get_characters(
page: int = Query(1, ge=1),
limit: int = Query(10, ge=1, le=100),
db: AsyncSession = Depends(get_db),
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

find . -name "pyproject.toml" -o -name "ruff.toml" | head -5

Repository: GC-MapleWind/MSGS_13_B

Length of output: 94


🏁 Script executed:

fd -type f -name "characters.py" | grep controller

Repository: GC-MapleWind/MSGS_13_B

Length of output: 236


🏁 Script executed:

cat -n controller/v1/characters.py

Repository: GC-MapleWind/MSGS_13_B

Length of output: 1427


🏁 Script executed:

cat -n pyproject.toml

Repository: GC-MapleWind/MSGS_13_B

Length of output: 413


🏁 Script executed:

cat -n ruff.toml

Repository: GC-MapleWind/MSGS_13_B

Length of output: 1182


Ruff B008 경고를 무시해야 합니다

Depends(get_db) 패턴은 FastAPI 의존성 주입의 공식 권장 방식이며, 코딩 가이드라인에서 명시적으로 요구합니다. 현재 ruff.toml의 ignore 리스트에 B008이 포함되어 있지 않아 경고가 발생하고 있습니다. ruff.toml의 ignore 리스트에 B008을 추가하거나, 해당 라인에 # noqa: B008을 추가하여 억제하세요.

🧰 Tools
🪛 Ruff (0.15.1)

[warning] 16-16: Do not perform function call Depends in argument defaults; instead, perform the call within the function, or read the default from a module-level singleton variable

(B008)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@controller/v1/characters.py` at line 16, The ruff B008 warning flags the use
of the FastAPI dependency pattern Depends(get_db) even though it's an approved
project convention; fix by either adding "B008" to the ignore list in ruff.toml
or by appending a per-line suppression comment to the dependency declaration
(e.g., add "# noqa: B008" to the line containing Depends(get_db)), ensuring the
symbol Depends(get_db) remains unchanged.

@@ -1,3 +1,4 @@
from typing import List
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion | 🟠 Major

typing.List 사용 금지 — Python 3.12 내장 list[] 사용 필요

from typing import ListList[CharacterResponse]는 가이드라인에서 명시적으로 금지된 패턴입니다. Python 3.12 내장 타입 구문을 사용해야 합니다.

🔧 수정 제안
-from typing import List
 from pydantic import BaseModel


 class CharacterPageResponse(BaseModel):
-    items: List[CharacterResponse]
+    items: list[CharacterResponse]
     total: int
     page: int
     limit: int

As per coding guidelines: "Do NOT use typing.Optional, typing.List, or typing.Annotated - use modern Python 3.12 syntax."

Also applies to: 20-20

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@schemas/character_dto.py` at line 1, Remove the import of typing.List and
replace any uses of List[...] with the native Python 3.12 generic builtin
list[...] (e.g., change List[CharacterResponse] to list[CharacterResponse]);
update imports in schemas/character_dto.py to drop "from typing import List" and
ensure any function signatures, class attributes, or type hints (e.g.,
CharacterResponse, CharacterDTO, or variables currently annotated with
List[...]) use the new list[...] syntax consistently.

return character


async def get_characters(db: AsyncSession, page: int, limit: int):
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

반환 타입 어노테이션 누락

코딩 가이드라인에 따르면 함수 파라미터와 반환 타입에 항상 타입 힌트를 작성해야 합니다. get_characters에 반환 타입이 없습니다.

🔧 수정 제안
-async def get_characters(db: AsyncSession, page: int, limit: int):
+async def get_characters(db: AsyncSession, page: int, limit: int) -> dict[str, Any]:

또는 CharacterPageResponse를 직접 반환하는 방식으로 개선하면 더 타입-안전합니다(아래 리팩터링 제안 참고).

As per coding guidelines: "Function parameters and return types must always be annotated with type hints."

📝 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
async def get_characters(db: AsyncSession, page: int, limit: int):
async def get_characters(db: AsyncSession, page: int, limit: int) -> dict[str, Any]:
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@services/character_service.py` at line 19, The function get_characters is
missing a return type annotation; update its signature (async def
get_characters(db: AsyncSession, page: int, limit: int) -> ...) to include the
correct return type—either a paginated response type like CharacterPageResponse
or a more explicit collection type (e.g., List[Character] / Sequence[Character])
depending on what the function actually returns; ensure imports for
CharacterPageResponse or typing types are added and adjust any internal returns
to match the declared type.

async def get_characters(db: AsyncSession, page: int, limit: int):
offset = (page - 1) * limit

# 기존 repo의 get_all을 그대로 재사용 (리스크 최소)
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

불필요한 주석 제거

# 기존 repo의 get_all을 그대로 재사용 (리스크 최소)는 코드 자체로 충분히 자명합니다. 가이드라인에 따르면 자명한 코드에 주석을 추가하지 않아야 합니다.

🔧 수정 제안
-    # 기존 repo의 get_all을 그대로 재사용 (리스크 최소)
     items = await character_repo.get_all(db, skip=offset, limit=limit)

As per coding guidelines: "Do NOT add comments or docstrings for self-explanatory code."

📝 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
# 기존 repo의 get_all을 그대로 재사용 (리스크 최소)
items = await character_repo.get_all(db, skip=offset, limit=limit)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@services/character_service.py` at line 22, Remove the unnecessary
self-explanatory inline comment "# 기존 repo의 get_all을 그대로 재사용 (리스크 최소)" in
services/character_service.py; locate the place where get_all is reused (the
call or wrapper named get_all) and delete that comment line so the code remains
clean and follows the "no comments for obvious code" guideline.

@sleegme sleegme requested a review from ark1st February 21, 2026 11:18
@ark1st
Copy link
Collaborator

ark1st commented Feb 21, 2026

dev로 바꿔주고, conflict 해결해주세요
(dev 를 pull 해오면 해결할 수 있음)

@ark1st ark1st changed the base branch from main to dev February 21, 2026 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants