improvements: adding more spaces related exports

[slkzgm]

This PR adds missing exports and applies formatting, replaces “broadcasts” with “spaces” for clickable space links, and moves guestReaction events from info to debug logs.

Summary by CodeRabbit

• New Features

  • Added new client and audio-related exports to the module
  • Expanded type exports

• Refactor

  • Updated logging levels in ChatClient
  • Reformatted logging statements across multiple plugins
  • Modified space initialization URL logging

• Style

  • Improved code formatting and readability in various files
  • Consistent indentation and log message presentation

[coderabbitai]

Walkthrough

The pull request introduces several minor modifications across multiple files in the src directory, focusing primarily on code formatting, logging adjustments, and export configurations. The changes include updating the module exports in _module.ts to include new clients and components, adjusting log levels and message formatting in various plugin and core files, and making subtle changes to URL representations in logging statements. These modifications aim to improve code readability, logging verbosity, and export structure without significantly altering the core functionality of the codebase.

Changes

File	Change Summary
src/_module.ts	Added new exports for JanusClient, JanusAudioSink, JanusAudioSource, and ChatClient. Updated type exports to include ./spaces/types.
src/spaces/core/ChatClient.ts	Changed guest reaction logging from info to debug level
src/spaces/core/Space.ts	Modified initialization log to replace "broadcasts" with "spaces" in share URL
src/spaces/plugins/*	Formatting and indentation improvements in HlsRecordPlugin, IdleMonitorPlugin, MonitorAudioPlugin, and RecordToDiskPlugin

Poem

🐰 A Rabbit's Code Refrain 🖥️

Exports dance, logs get neat,
Formatting makes the code so sweet
Plugins aligned with rabbit's care
Debugging whispers everywhere
Clean code hops with gentle might!

Finishing Touches

• 📝 Generate Docstrings (Beta)

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

src/_module.ts (1)

7-17: LGTM! Well-organized exports.

The new exports for spaces-related functionality are properly grouped together, making the module's interface clear and maintainable.

Consider grouping the exports into logical sections with comments for better organization:

 // Core types
 export type { Profile } from './profile';
+
+// Space-related exports
 export { Space } from './spaces/core/Space';
 export { SpaceParticipant } from './spaces/core/SpaceParticipant';

src/spaces/core/Space.ts (1)

174-177: LGTM! Improved URL clarity in logs.

The URL transformation from 'broadcasts' to 'spaces' aligns with the platform's terminology.

Consider extracting the URL transformation to a utility function for reusability and maintainability:

+const getSpaceUrl = (url: string) => url.replace('broadcasts', 'spaces');
+
 this.logger.info(
   '[Space] Initialized =>',
-  broadcast.share_url.replace('broadcasts', 'spaces'),
+  getSpaceUrl(broadcast.share_url),
 );

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6678581 and 66e7c23.

📒 Files selected for processing (7)

• src/_module.ts (1 hunks)
• src/spaces/core/ChatClient.ts (1 hunks)
• src/spaces/core/Space.ts (1 hunks)
• src/spaces/plugins/HlsRecordPlugin.ts (9 hunks)
• src/spaces/plugins/IdleMonitorPlugin.ts (3 hunks)
• src/spaces/plugins/MonitorAudioPlugin.ts (4 hunks)
• src/spaces/plugins/RecordToDiskPlugin.ts (2 hunks)

✅ Files skipped from review due to trivial changes (5)

• src/spaces/plugins/RecordToDiskPlugin.ts
• src/spaces/plugins/IdleMonitorPlugin.ts
• src/spaces/core/ChatClient.ts
• src/spaces/plugins/MonitorAudioPlugin.ts
• src/spaces/plugins/HlsRecordPlugin.ts

🔇 Additional comments (1)

src/_module.ts (1)

19-20: LGTM! Comprehensive type exports.

The addition of spaces/types export ensures all space-related types are available to consumers.

[wtfsayo]

Can you add a log/test if ffmpeg isn't found