fix: lint

[lovegaoshi]

Summary by CodeRabbit

• New Features

  • Enhanced logout functionality in the Explore component.
  • Improved cookie management during navigation events in the Login component.

• Bug Fixes

  • Adjusted cookie handling to ensure proper saving for the YouTube domain.

• Chores

  • Updated multiple package dependencies for improved performance and security.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
azusa-player-mobile	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 4, 2024 6:34pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request includes updates to the package.json file for the azusa-player-mobile project, where multiple dependencies and devDependencies have had their version numbers incremented. Additionally, modifications were made to the logout functionality in the Explore component and cookie management in the Login component. The useYTMLogin hook was also updated by removing the clearMuseCookies function, simplifying the error handling and user state management.

Changes

File Path	Change Summary
package.json	Updated multiple dependencies and devDependencies to newer versions.
src/components/login/google/YTM.tsx	Modified logout functionality to ensure initMuse is called after promise resolution; improved cookie handling in onBackPress.
src/components/login/google/useYTMLogin.ts	Removed clearMuseCookies function, simplifying the refresh function's logic related to cookie management.

Possibly related PRs

• chore: dep upg #536: This PR also updates the package.json file, specifically modifying dependency versions, which is directly related to the changes made in the main PR.
• fix: ghactions oos #640: Although primarily focused on GitHub Actions, this PR mentions updates to the workflow that may indirectly relate to the overall project management, but it does not directly affect the package.json changes.
• feat: lint check on PR #668: This PR introduces a new linting workflow that could be relevant for maintaining code quality in conjunction with the dependency updates in the main PR, but it does not directly modify package.json.

🐰 In the garden, changes bloom,
Dependencies rise, dispelling gloom.
Logout refined, cookies now stay,
With each new version, we hop and play!
A leap for the code, a joyful cheer,
Progress is here, let’s all draw near! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between a572c61 and a3e6b02.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (3)

• package.json (4 hunks)
• src/components/login/google/YTM.tsx (1 hunks)
• src/components/login/google/useYTMLogin.ts (0 hunks)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud