[frontend] refactor online status provider

[kotto5]

online-status の管理を、client-socket-provider() から、useOnlineStatus() に移譲しました。

[coderabbitai]

Walkthrough

The recent update involves refactoring the management and context of online status across the frontend. The creation and handling of OnlineContext have been moved from client-socket-provider.tsx to useOnlineStatus.ts, centralizing online status logic. client-socket-provider.tsx now focuses on socket connections without directly managing online status. Changes in onlineProviders.tsx and user-list.tsx align with these updates, ensuring that online status management is consistent and streamlined throughout the application.

Changes

File Path	Change Summary
.../client-socket-provider.tsx	Removed OnlineContext creation and setOnlineStatus prop; moved online status logic to handleOnlineStatus.
.../hooks/useOnlineStatus.ts	Added OnlineContext creation; integrated socket handling for online status updates.
.../onlineProviders.tsx	Updated import and usage of useOnlineStatus, removing direct use of setOnlineStatus.
.../ui/user/user-list.tsx	Updated OnlineContext import to source from useOnlineStatus instead of client-socket-provider.

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.

[coderabbitai]

Ensure imports are correctly ordered according to the project's coding standards, typically with external libraries first, followed by internal modules.

[coderabbitai]

Ensure that all hooks and utilities are used correctly and efficiently, following React best practices for hooks usage and side effects management.