[frontend] Refactoring of socket event handling for room action

[lim396]

• roomのアクション(enter、leaveなど)関連のsocketイベントハンドリングをclient-socket-provider.tsxから削除し、実際にハンドリンが必要な場所に移動させました。

[coderabbitai]

Walkthrough

The recent update enhances room management and navigation within the application. It introduces a new component ExploreRooms for displaying and managing room exploration, streamlines the handling of room events like deletion and entry through a consolidated event handler, and refines navigation by updating the router in response to specific user actions. The changes focus on improving user experience by simplifying the interface and making room interactions more intuitive and responsive.

Changes

File(s)	Change Summary
frontend/.../explore-rooms.tsx, frontend/.../explore-rooms/page.tsx	Introduced ExploreRooms component for room display and management; refactored to use ExploreRooms for rendering.
frontend/.../client-socket-provider.tsx	Refined room event handling with a consolidated event handler and simplified cleanup logic.
frontend/.../hooks/useKick.ts	Enhanced useKick hook to handle LeaveRoomEvent and included meId parameter for improved logic.
frontend/.../[id]/sidebar-item.tsx, frontend/.../rooms-sidebar.tsx	Added handling for EnterRoomEvent and DeleteRoomEvent, including event listeners and cleanup, improved navigation by refreshing router on specific events.

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>.
  • Generate unit-tests for this file.
• 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 tests 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 generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.