[BE-FEAT] 재로그인 시 구글 캘린더 일정 가져오기 기능 추가

[kwon204]

#️⃣ 연관된 이슈>

• [Feature] 재로그인 시 구글 캘린더 일정 가져오기 기능 #402

📝 작업 내용> 이번 PR에서 작업한 내용을 간략히 설명해주세요(이미지 첨부 가능)

• 로그인하면 syncWithCalendar()를 호출하도록 하였습니다.

🙏 여기는 꼭 봐주세요! > 리뷰어가 특별히 봐주었으면 하는 부분이 있다면 작성해주세요

Summary by CodeRabbit

• Bug Fixes

  • Improved Google Calendar subscription process to ensure immediate synchronization after subscribing, keeping calendar data up to date.

• Tests

  • Updated tests to verify enhanced synchronization and retry behavior during Google Calendar subscription renewal.

[coderabbitai]

Walkthrough

The subscribeGoogleCalendar method in GoogleCalendarService was updated to immediately synchronize the calendar after subscribing. Corresponding unit tests were adjusted to expect two retry executions, reflecting the new sync call post-subscription. No changes were made to method signatures or public interfaces.

Changes

File(s)	Change Summary
backend/src/main/java/endolphin/backend/global/google/GoogleCalendarService.java	Modified subscribeGoogleCalendar to call syncWithCalendar after subscribing to ensure immediate sync.
backend/src/test/java/endolphin/backend/global/google/GoogleCalendarServiceTest.java	Updated test to verify that retry logic is executed twice, reflecting the additional sync call post-subscribe.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GoogleCalendarService
    participant GoogleAPI

    User->>GoogleCalendarService: subscribeGoogleCalendar(user)
    GoogleCalendarService->>GoogleAPI: Subscribe to Calendar
    GoogleCalendarService->>GoogleAPI: syncWithCalendar(calendarId, user)

Loading

Possibly related PRs

• [BE-Hotfix] 디버깅 로그 추가 #239: Adds logging inside syncWithCalendar, directly related to the method now being called after subscription.
• [BE-Feat] 캘린더 api 사용 로직 구현 #139: Introduces the syncWithCalendar method, which is now invoked post-subscription in the updated logic.
• [BE-Hotfix] 디버깅 로그 추가 #242: Adds logging to syncWithCalendar and related methods, touching on the same synchronization workflow.

Suggested reviewers

• efdao

Poem

A calendar sync after subscribe,
Keeps your schedule fresh and alive.
With two retries, the tests agree,
The code now hums in harmony.
🐇⏰✨

Hopping forward, up-to-date—
No more events left to fate!

Tip

⚡️ 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 094822f and 93405e9.

📒 Files selected for processing (2)

• backend/src/main/java/endolphin/backend/global/google/GoogleCalendarService.java (1 hunks)
• backend/src/test/java/endolphin/backend/global/google/GoogleCalendarServiceTest.java (1 hunks)

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

• GitHub Check: backend

🔇 Additional comments (2)

backend/src/main/java/endolphin/backend/global/google/GoogleCalendarService.java (1)

65-69: Excellent enhancement to synchronize Google Calendar immediately after subscribing!

The addition of the syncWithCalendar call ensures that calendar data is fetched right after subscription during re-login, satisfying the PR objective. This maintains data consistency by guaranteeing users have the latest calendar events immediately available after logging in again.

backend/src/test/java/endolphin/backend/global/google/GoogleCalendarServiceTest.java (1)

93-115: Test correctly updated to verify the new synchronization behavior

The test has been properly updated to verify that retryExecutor.executeCalendarApiWithRetry is called twice (instead of once) when handling expired subscriptions - once for subscription renewal and once for the newly added calendar synchronization.

✨ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

[efdao]

👍