Skip to content

Conversation

@youz2me
Copy link
Member

@youz2me youz2me commented Jun 30, 2025

👻 PULL REQUEST

📄 작업 내용

  • 정기 회의에서 추가된 컨벤션을 바탕으로 리드미를 수정했어요.
  • 정기 회의에서 추가된 컨벤션을 바탕으로 PR 템플릿의 코드 리뷰 체크리스트를 추가했어요.

🔗 연결된 이슈

Summary by CodeRabbit

  • Documentation
    • Updated the pull request template with a new section for reviewer notes and added a detailed code review checklist.
    • Completely revised and expanded the README to provide a comprehensive coding convention and style guide, including rules for formatting, naming, structure, and performance optimization for the iOS project.

@youz2me youz2me requested a review from JinUng41 June 30, 2025 15:06
@youz2me youz2me self-assigned this Jun 30, 2025
@youz2me youz2me added 📝 docs README, 템플릿 등 프로젝트 내 문서 수정 시 사용 🦉 유진 🛌🛌🛌🛌🛌🛌🛌🛌🛌🛌 labels Jun 30, 2025
@coderabbitai
Copy link

coderabbitai bot commented Jun 30, 2025

Walkthrough

The pull request updates the README.md to provide a detailed, formalized coding convention and style guide for the iOS project, replacing previous fragmented notes. Additionally, the pull request template is revised to improve review guidance and add a comprehensive code review checklist. No code or exported entity changes are introduced.

Changes

File(s) Change Summary
README.md Rewritten and expanded as a comprehensive coding convention and style guide for the iOS project.
.github/PULL_REQUEST_TEMPLATE.md Updated review sections and added a detailed code review checklist for PR reviewers.

Assessment against linked issues

Objective Addressed Explanation
Update README based on revised conventions (#255)

Poem

🐰
A README renewed, so crisp and so neat,
With guidelines and checklists—no coder can cheat!
From lazy vars to MARKs in a row,
Our code style now sparkles, in orderly flow.
The rabbit approves, with a hop and a cheer,
For conventions like these bring code ever near!


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: 1

🧹 Nitpick comments (1)
README.md (1)

204-210: Consider enforcing the basic rules with SwiftLint / SwiftFormat
The section introduces max-line-length and indentation limits, but the repo will keep diverging unless the rules are machine-enforced. Adding a .swiftlint.yml / swiftformat config (or Xcode build-phase script) that reflects these numbers will prevent manual drift and reduce review noise.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 048f3c2 and 8a3cab6.

📒 Files selected for processing (2)
  • .github/PULL_REQUEST_TEMPLATE.md (1 hunks)
  • README.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md

254-254: Hard tabs
Column: 1

(MD010, no-hard-tabs)

🔇 Additional comments (1)
.github/PULL_REQUEST_TEMPLATE.md (1)

33-49: 👍 Comprehensive checklist aligns with new convention
The added items map 1-to-1 with the README rules and will help keep reviews focused. Nice touch including memory-leak & import-order points.

Comment on lines +250 to +264
`Setup` 관련 메서드는 다음 명명 규칙과 역할에 따라 구분하여 작성한다.
아래 순서대로 차례대로 작성한다.

<div align="center">

| 메서드명 | 역할 및 담당 업무 |
|---|---|
| `setupNavigationBar()` | 네비게이션 바 설정 및 구성 |
| `setupView()` | 해당 클래스의 프로퍼티 관리, 기본 뷰 설정 |
| `setupConstraints()` | addSubviews, SnapKit 등 오토레이아웃 관련 코드 |
| `setupAction()` | 액션 이벤트 관련 설정 |
| `setupDelegate()` | Delegate, DataSource 관련 코드 |
| `setupDataSource()` | 데이터 소스 초기화 및 설정 |
| `setupBinding()` | 데이터 바인딩 및 리액티브 프로그래밍 관련 코드 |

Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Replace hard tabs with spaces to satisfy markdown-lint (MD010)
Static analysis flags a tab character in this table. Tabs cause inconsistent rendering on GitHub and break the “no hard tabs” rule now encoded in CI.

-	| 메서드명 | 역할 및 담당 업무 |
+| 메서드명 | 역할 및 담당 업무 |

Run a quick sed -i '' $'s/\t/ /g' README.md (or your editor’s “convert to spaces”) before merge.

📝 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
`Setup` 관련 메서드는 다음 명명 규칙과 역할에 따라 구분하여 작성한다.
아래 순서대로 차례대로 작성한다.
<div align="center">
| 메서드명 | 역할 및 담당 업무 |
|---|---|
| `setupNavigationBar()` | 네비게이션 바 설정 및 구성 |
| `setupView()` | 해당 클래스의 프로퍼티 관리, 기본 뷰 설정 |
| `setupConstraints()` | addSubviews, SnapKit 등 오토레이아웃 관련 코드 |
| `setupAction()` | 액션 이벤트 관련 설정 |
| `setupDelegate()` | Delegate, DataSource 관련 코드 |
| `setupDataSource()` | 데이터 소스 초기화 및 설정 |
| `setupBinding()` | 데이터 바인딩 및 리액티브 프로그래밍 관련 코드 |
`Setup` 관련 메서드는 다음 명명 규칙과 역할에 따라 구분하여 작성한다.
아래 순서대로 차례대로 작성한다.
<div align="center">
| 메서드명 | 역할 및 담당 업무 |
|---|---|
| `setupNavigationBar()` | 네비게이션 바 설정 및 구성 |
| `setupView()` | 해당 클래스의 프로퍼티 관리, 기본 뷰 설정 |
| `setupConstraints()` | addSubviews, SnapKit 등 오토레이아웃 관련 코드 |
| `setupAction()` | 액션 이벤트 관련 설정 |
| `setupDelegate()` | Delegate, DataSource 관련 코드 |
| `setupDataSource()` | 데이터 소스 초기화 및 설정 |
| `setupBinding()` | 데이터 바인딩 및 리액티브 프로그래밍 관련 코드 |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

254-254: Hard tabs
Column: 1

(MD010, no-hard-tabs)

🤖 Prompt for AI Agents
In README.md around lines 250 to 264, replace all hard tab characters in the
markdown table with spaces to comply with markdown-lint rule MD010 and ensure
consistent rendering on GitHub. Use a command like `sed -i '' $'s/\t/  /g'
README.md` or your editor's convert-to-spaces feature to perform this
replacement before merging.

Copy link
Collaborator

@JinUng41 JinUng41 left a comment

Choose a reason for hiding this comment

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

굿~ 너무 좋은데요.
감사합니다! 👍🏼

@github-project-automation github-project-automation bot moved this to In Review in Wable-iOS Jun 30, 2025
@youz2me youz2me merged commit e96914e into develop Jun 30, 2025
1 check passed
@github-project-automation github-project-automation bot moved this from In Review to Done in Wable-iOS Jun 30, 2025
@youz2me youz2me deleted the docs/#255-readme branch June 30, 2025 15:15
youz2me added a commit that referenced this pull request Oct 26, 2025
[Docs] 추가된 컨벤션에 따른 리드미 수정 및 코드 리뷰 체크리스트 추가
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📝 docs README, 템플릿 등 프로젝트 내 문서 수정 시 사용 🦉 유진 🛌🛌🛌🛌🛌🛌🛌🛌🛌🛌

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[Docs] 수정된 컨벤션 기반 리드미 수정

3 participants