[YS-535] feat: experimentPost 테이블 title 컬럼 길이 150자로 확장

[Ji-soo708]

💡 작업 내용

• experimentPost 테이블 title 컬럼 길이 150자로 확장

✅ 셀프 체크리스트

• PR 제목을 형식에 맞게 작성했나요?
• 브랜치 전략에 맞는 브랜치에 PR을 올리고 있나요?
• 테스트는 잘 통과했나요?
• 빌드에 성공했나요?
• 본인을 assign 해주세요.
• 해당 PR에 맞는 label을 붙여주세요.

🙋🏻‍ 확인해주세요

• 빠른 반영을 위해 리뷰없이 바로 머지하겠습니다~

🔗 Jira 티켓

---

https://yappsocks.atlassian.net/browse/YS-535

Summary by CodeRabbit

• New Features
  • 실험 게시글의 제목 입력 가능 글자 수가 70자에서 150자로 확장되었습니다. 이제 더 긴 제목을 입력할 수 있습니다.

[coderabbitai]

Walkthrough

ExperimentPostEntity의 title 컬럼 길이가 70자에서 150자로 확장되었습니다. 이에 따라 엔티티 클래스의 어노테이션과 데이터베이스 마이그레이션 스크립트가 수정되어 더 긴 제목을 저장할 수 있게 되었습니다. 추가적인 로직 변경은 없습니다.

Changes

Cohort / File(s)	Change Summary
Entity 컬럼 길이 확장 infrastructure/src/main/kotlin/com/dobby/persistence/entity/experiment/ExperimentPostEntity.kt	ExperimentPostEntity의 title 필드 길이 제한을 70자에서 150자로 변경
DB 마이그레이션 infrastructure/src/main/resources/db/migration/V202508031601__extend_title_length_in_experiment_post.sql	experiment_post 테이블의 title 컬럼을 VARCHAR(150) NOT NULL로 변경하는 마이그레이션 추가

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰
제목이 길어져 기쁜 토끼,
실험 기록 더 풍성해졌지!
title에 담긴 이야기,
이제는 넉넉히 펼치리.
코드는 가볍게,
리뷰도 빠르게,
오늘도 변화에 깡총깡총!

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 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 1836990 and a5a9d0e.

📒 Files selected for processing (2)

• infrastructure/src/main/kotlin/com/dobby/persistence/entity/experiment/ExperimentPostEntity.kt (1 hunks)
• infrastructure/src/main/resources/db/migration/V202508031601__extend_title_length_in_experiment_post.sql (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: Ji-soo708
PR: YAPP-Github/Gradmeet-BE#140
File: domain/src/main/kotlin/com/dobby/gateway/auth/GoogleAuthGateway.kt:7-7
Timestamp: 2025-06-04T09:02:40.657Z
Learning: Ji-soo708의 팀은 로컬 ktlint 기준과 GitHub ktlint 체크 기준이 다를 때, 기존 코드베이스와의 일관성을 위해 로컬 기준을 우선시한다.

Learnt from: Ji-soo708
PR: YAPP-Github/Gradmeet-BE#154
File: infrastructure/src/main/kotlin/com/dobby/mapper/ExperimentPostKeywordsLogMapper.kt:15-22
Timestamp: 2025-07-27T12:37:15.372Z
Learning: Ji-soo708의 팀에서는 JSON 역직렬화 시 예외를 catch하여 래핑하기보다는, 예외를 자연스럽게 상위로 전파시켜 원본 컨텍스트를 보존하고 후속 조치를 용이하게 하는 것을 선호한다.

📚 Learning: gradmeet-be 프로젝트에서 participant 및 experiment_post 테이블의 region 관련 컬럼에는 `*_all` 형태의 enum 값이 실제 데이터로 존재하...

Learnt from: Ji-soo708
PR: YAPP-Github/Gradmeet-BE#152
File: infrastructure/src/main/resources/db/migration/V202507231332__remove_all_enum_values_from_participant_and_experiment_post.sql:1-55
Timestamp: 2025-07-23T04:54:17.284Z
Learning: Gradmeet-BE 프로젝트에서 participant 및 experiment_post 테이블의 region 관련 컬럼에는 `*_ALL` 형태의 ENUM 값이 실제 데이터로 존재하지 않으므로, 해당 값들을 제거하는 ALTER TABLE MODIFY COLUMN 구문은 데이터 정합성 문제 없이 안전하게 실행될 수 있다.

Applied to files:

• infrastructure/src/main/resources/db/migration/V202508031601__extend_title_length_in_experiment_post.sql

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (2)

infrastructure/src/main/resources/db/migration/V202508031601__extend_title_length_in_experiment_post.sql (1)

1-1: 인덱스 정의 없음 – VARCHAR(150) 확장 안전합니다
마이그레이션 파일에서 experiment_post.title을 참조하는 별도 CREATE INDEX나 inline KEY 정의를 확인한 결과가 없습니다. 따라서 VARCHAR(150) 확장은 인덱스 길이 한도(767B)를 초과하지 않아 문제없이 적용 가능합니다.

infrastructure/src/main/kotlin/com/dobby/persistence/entity/experiment/ExperimentPostEntity.kt (1)

44-45: 엔티티와 스키마가 일치합니다

length = 150 설정이 마이그레이션과 일관되며, 추가 수정 사항은 없습니다. 👍

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/YS-535

---

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 generate unit tests to generate unit tests for 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.