🚀 release: v0.2.0 beta #14
Conversation
…n webhook messages
WalkthroughThe changes update configuration files, documentation, and various source modules. The environment file now includes new variables for forum channel IDs and debug mode, while the repository ignore rules have been modified. The README details a new feature that automatically creates support tickets from forum posts. User-facing modifications mark the support email input as optional. Multiple modules have been updated to use a structured logging framework via a new logger utility. Additionally, event handlers and service modules now implement refined workflows—such as enhanced email handling, early exits for forum posts, and an exponential backoff strategy for ticket polling. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Discord
participant Bot
participant Unthread
participant Logger
User->>Discord: Start forum thread (post)
Discord->>Bot: Emit threadCreate event with thread details
Bot->>Logger: Log thread creation event
Bot->>Unthread: Request support ticket creation with thread info
Unthread-->>Bot: Return ticket confirmation details
Bot->>Discord: Post confirmation embed in thread
Bot->>Logger: Log ticket creation success
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🔭 Outside diff range comments (1)
src/services/unthread.js (1)
236-406: 🛠️ Refactor suggestionWebhook event handler improvements.
- Logging enhancements make error tracing easier, especially for conversation status changes and duplicate detection.
- Skipping attachments and duplicates is a clever solution to avoid redundant messages. However, relying on the last 10 messages could miss older duplicates in long-lived threads. If long threads are anticipated, consider a more robust approach (e.g., searching by message ID or a broader fetch range).
- Overall, the error handling flow is clean and consistent with the rest of the codebase.
🧰 Tools
🪛 Biome (1.9.4)
[error] 329-329: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
🧹 Nitpick comments (11)
README.md (1)
97-108: Helpful configuration instructions for the forum channel feature.The section provides clear steps for enabling and configuring the automatic ticket creation from forum posts.
Add a language specifier to the code block on line 102 to fix the markdown linting issue:
- ``` + ```env FORUM_CHANNEL_IDS=123456789012345678,234567890123456789 ```🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
102-102: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
src/events/messageCreate.js (2)
17-21: Effective implementation of forum post detection and early exit.This logic correctly identifies messages from forum posts using the configured channel IDs and prevents them from being processed further, which is essential for the new automatic ticket creation feature.
Consider using optional chaining to simplify the condition:
- const isForumPost = FORUM_CHANNEL_IDS && - FORUM_CHANNEL_IDS.split(',').includes(message.channel.parentId) && - message.id === message.channel.id; + const isForumPost = FORUM_CHANNEL_IDS?.split(',').includes(message.channel.parentId) && + message.id === message.channel.id;🧰 Tools
🪛 Biome (1.9.4)
[error] 17-18: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
28-38: Improved quoted message handling with better error logging.The restructuring of the quoted message handling with the logger integration improves error visibility and maintainability.
Use optional chaining for checking message reference:
- if (message.reference && message.reference.messageId) { + if (message.reference?.messageId) {🧰 Tools
🪛 Biome (1.9.4)
[error] 29-29: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
src/deploy_commands.js (1)
27-27: Check for potential command definition confusion.Using
logger.warnhere is appropriate to highlight a missingdataorexecuteproperty. Consider adding guidance on how to fix the command definition within the warning message to assist developers quickly.src/utils/logger.js (1)
19-40: Debug function logic.Conditionally logging debug messages with a prefixed label is neat. However, be mindful of situations where
DEBUG_MODEmight be set to non-lowercase values like'TRUE'. If that's a concern, ensure you standardize or sanitize environment inputs.src/events/threadCreate.js (2)
13-14: Forum channel configuration handling.Splitting
process.env.FORUM_CHANNEL_IDSby comma is straightforward. Consider trimming the results in case there are accidental spaces.const FORUM_CHANNEL_IDS = process.env.FORUM_CHANNEL_IDS ? - process.env.FORUM_CHANNEL_IDS.split(',') : []; + process.env.FORUM_CHANNEL_IDS.split(',').map(id => id.trim()) : [];
25-47: Customer data retrieval and creation.Fetching or creating a default customer record, plus deriving an email address, is logical. Watch for collisions if multiple users share the same username.
src/events/interactionCreate.js (3)
16-37: Consider validating user email.The fallback mechanism is a practical approach to handle empty emails. However, if email validity is important, adding a basic format check or user prompt could reduce confusion. Otherwise, storing a placeholder domain is fine, as long as it doesn't break downstream logic expecting real domains.
38-94: Robust ticket creation workflow.The step-by-step approach with try/catch and deferred reply for ephemeral interaction is well-structured. Consider whether you need a cleanup routine if thread creation fails after the ticket is already created. That can prevent leftover tickets in the Unthread system if errors occur mid-flow.
96-132: Command handling logic is well-organized.Checking the interaction state (replied or deferred) before using followUp or reply is a reliable pattern. You might also consider adding user context (e.g., user.id) to the error logs for debugging multi-user concurrency issues, but this is optional.
src/services/unthread.js (1)
129-180: Exponential backoff logic is correctly implemented.The increased max retries and the jitter factor help mitigate potential rate limit collisions. This strategy is sound. Ensure the exponential bounds are acceptable performance-wise so that user experience isn’t unduly delayed when friendlyId fails to appear.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (14)
.env.example(1 hunks).gitignore(1 hunks)README.md(2 hunks)src/commands/support/support.js(1 hunks)src/deploy_commands.js(3 hunks)src/events/error.js(1 hunks)src/events/interactionCreate.js(1 hunks)src/events/messageCreate.js(3 hunks)src/events/ready.js(2 hunks)src/events/threadCreate.js(1 hunks)src/index.js(5 hunks)src/services/unthread.js(9 hunks)src/services/webhook.js(2 hunks)src/utils/logger.js(1 hunks)
🧰 Additional context used
🧬 Code Definitions (8)
src/services/webhook.js (8)
src/services/unthread.js (4)
logger(12-12)require(9-9)require(10-10)require(11-11)src/index.js (3)
logger(8-8)require(3-3)require(7-7)src/events/interactionCreate.js (4)
logger(4-4)require(1-1)require(2-2)require(3-3)src/deploy_commands.js (2)
logger(4-4)require(1-1)src/events/threadCreate.js (4)
logger(8-8)require(5-5)require(6-6)require(7-7)src/events/messageCreate.js (4)
logger(5-5)require(1-1)require(2-2)require(3-3)src/events/error.js (2)
logger(2-2)require(1-1)src/events/ready.js (1)
logger(3-3)
src/events/messageCreate.js (7)
src/services/unthread.js (9)
logger(12-12)require(9-9)require(10-10)require(11-11)customer(63-69)customer(100-100)response(29-36)response(102-122)response(423-444)src/events/ready.js (2)
logger(3-3)require(1-1)src/events/threadCreate.js (6)
logger(8-8)require(5-5)require(6-6)require(7-7)FORUM_CHANNEL_IDS(13-14)src/events/interactionCreate.js (5)
logger(4-4)require(1-1)require(2-2)require(3-3)src/events/error.js (2)
logger(2-2)require(1-1)src/services/webhook.js (1)
logger(3-3)src/utils/database.js (1)
require(6-6)
src/events/error.js (8)
src/deploy_commands.js (2)
logger(4-4)require(1-1)src/events/messageCreate.js (4)
logger(5-5)require(1-1)require(2-2)require(3-3)src/events/ready.js (2)
logger(3-3)require(1-1)src/index.js (3)
logger(8-8)require(3-3)require(7-7)src/events/interactionCreate.js (4)
logger(4-4)require(1-1)require(2-2)require(3-3)src/events/threadCreate.js (4)
logger(8-8)require(5-5)require(6-6)require(7-7)src/services/webhook.js (2)
logger(3-3)require(1-1)src/services/unthread.js (3)
logger(12-12)require(9-9)require(10-10)
src/events/threadCreate.js (6)
src/events/interactionCreate.js (6)
require(1-1)require(2-2)require(3-3)logger(4-4)thread(58-62)ticket(44-44)src/services/unthread.js (6)
require(9-9)require(10-10)require(11-11)logger(12-12)messages(323-323)ticket(197-197)src/events/messageCreate.js (5)
require(1-1)require(2-2)require(3-3)logger(5-5)process(4-4)src/index.js (4)
require(3-3)require(7-7)logger(8-8)process(13-13)src/events/error.js (2)
require(1-1)logger(2-2)src/events/ready.js (2)
require(1-1)logger(3-3)
src/deploy_commands.js (8)
src/events/messageCreate.js (4)
logger(5-5)require(1-1)require(2-2)require(3-3)src/events/error.js (2)
logger(2-2)require(1-1)src/events/ready.js (2)
logger(3-3)require(1-1)src/index.js (3)
logger(8-8)require(3-3)require(7-7)src/events/interactionCreate.js (4)
logger(4-4)require(1-1)require(2-2)require(3-3)src/events/threadCreate.js (4)
logger(8-8)require(5-5)require(6-6)require(7-7)src/services/webhook.js (2)
logger(3-3)require(1-1)src/services/unthread.js (3)
logger(12-12)require(9-9)require(10-10)
src/services/unthread.js (8)
src/events/messageCreate.js (4)
logger(5-5)require(1-1)require(2-2)require(3-3)src/index.js (3)
logger(8-8)require(3-3)require(7-7)src/events/threadCreate.js (4)
logger(8-8)require(5-5)require(6-6)require(7-7)src/events/interactionCreate.js (4)
logger(4-4)require(1-1)require(2-2)require(3-3)src/services/webhook.js (2)
logger(3-3)require(1-1)src/events/ready.js (2)
logger(3-3)require(1-1)src/deploy_commands.js (1)
logger(4-4)src/events/error.js (1)
logger(2-2)
src/index.js (8)
src/services/unthread.js (4)
logger(12-12)require(9-9)require(10-10)require(11-11)src/events/ready.js (2)
logger(3-3)require(1-1)src/events/messageCreate.js (4)
logger(5-5)require(1-1)require(2-2)require(3-3)src/events/threadCreate.js (4)
logger(8-8)require(5-5)require(6-6)require(7-7)src/services/webhook.js (2)
logger(3-3)require(1-1)src/deploy_commands.js (2)
logger(4-4)require(1-1)src/events/error.js (2)
logger(2-2)require(1-1)src/events/interactionCreate.js (3)
logger(4-4)require(1-1)require(2-2)
src/events/interactionCreate.js (4)
src/events/threadCreate.js (7)
require(5-5)require(6-6)require(7-7)logger(8-8)existingCustomer(41-41)ticket(49-49)src/services/unthread.js (5)
require(9-9)require(10-10)require(11-11)logger(12-12)ticket(197-197)src/events/messageCreate.js (5)
require(1-1)require(2-2)require(3-3)logger(5-5)src/events/error.js (2)
require(1-1)logger(2-2)
🪛 Biome (1.9.4)
src/events/messageCreate.js
[error] 17-18: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 29-29: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
🪛 markdownlint-cli2 (0.17.2)
README.md
102-102: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
🔇 Additional comments (39)
.gitignore (2)
136-136: Good addition for database files.Adding
*.sqliteto the ignore list is a good practice as database files should not typically be version controlled. This prevents accidental commits of development or test databases.
138-139: Appropriate exclusion of editor-specific settings.Ignoring
.vscode/settings.jsonis a good practice as it prevents user-specific editor configurations from being shared across the team.src/events/ready.js (2)
3-3: Good implementation of structured logging.Adding the logger utility import is consistent with the PR objective of improving logging throughout the codebase. This structured approach is better than direct console logging.
20-20: Appropriate replacement of console.log with logger.Replacing the console.log statement with logger.info maintains the same logging functionality while providing more consistent formatting and potentially better log management capabilities.
.env.example (2)
9-9: Well-structured configuration for forum channels.The addition of
FORUM_CHANNEL_IDSaligns with the PR objective of supporting automatic ticket creation from forum posts. Using a comma-separated list is an appropriate pattern for multiple IDs.
10-10: Useful debug mode configuration.Adding a
DEBUG_MODEenvironment variable provides a clean way to toggle additional logging or debugging features. Setting the default tofalseis appropriate for production environments.src/events/error.js (3)
2-2: Good implementation of structured logging.Adding the logger utility import is consistent with the PR objective of improving logging throughout the codebase.
8-8: Appropriate replacement of console logging with structured logging.Using
logger.errorinstead of console output is a better practice for error handling. This approach allows for more consistent error tracking and potentially easier integration with monitoring tools.
1-10:✅ Verification successful
Verify consistency of logger imports across files.
While this file correctly imports the logger, I noticed a potential inconsistency in how the logger is imported in different files based on the provided snippets.
🏁 Script executed:
#!/bin/bash # Check for consistency in logger imports across files echo "Checking logger import consistency..." # Search for logger imports in event files echo "Logger imports in event files:" rg --type js "const logger =" src/events/ -A 1 # Look for potential incorrect imports (without require) echo "Potentially incorrect logger imports:" rg --type js "const logger = \"\.\./utils/logger\"" src/Length of output: 859
Logger imports are consistent across event files.
The verification script confirms that all event files (e.g.,threadCreate.js,ready.js, etc.) correctly import the logger usingrequire('../utils/logger'). There is no inconsistency in the logger import approach, so no changes are necessary forsrc/events/error.jsor other related files.src/commands/support/support.js (1)
37-40: Good UX improvement making email optional!This change allows users to submit support tickets without requiring an email address. Make sure the fallback email mechanism (
username@discord.user) is consistently implemented across all related components.src/services/webhook.js (3)
3-3: Good logging standardization by importing the logger utility.Consistent with the PR's goal of improving logging throughout the codebase.
17-17: Improved logging approach for webhook debugging.Using the structured logger.debug method instead of console.log is more consistent and provides better control over log levels.
19-19: Enhanced error logging for signature verification failures.Using logger.error instead of console.error provides better error logging capabilities and consistency.
README.md (1)
14-14: Good documentation of the new automatic ticket creation feature.Clear explanation of the new capability for creating tickets from forum posts.
src/events/messageCreate.js (6)
4-5: Good addition of environment variables and logger import.These imports support the new forum post handling feature and improved logging system.
40-56: Great enhancement: Added support for message attachments.This implementation detects and categorizes attachment types (image, video, file) and adds them as links to the message, providing a more complete representation of the original Discord message in Unthread.
61-61: Good implementation of email fallback mechanism.This line properly supports the optional email field change by providing a fallback email using the Discord username when no customer email is available.
63-69: Improved message forwarding with structured logging.The enhanced logging approach provides better visibility into the message forwarding process.
72-72: Enhanced error logging for Unthread message sending failures.Using the structured logger improves error tracking and debugging capabilities.
85-85: Consistent logging improvements for command responses.Changed console logging to use the structured logger for better consistency and control.
Also applies to: 91-91
src/deploy_commands.js (3)
4-4: Adopt consistent logger usage here.Good job importing
loggerand maintaining consistency with the rest of the codebase. This ensures all logging goes through the same utility.
38-38: Great switch from console.log to logger.info.These info-level messages are more structured and align with your new logging approach. No further concerns.
Also applies to: 46-46
49-49: Use logger.error for all unexpected failures.Replacing
console.errorwithlogger.errorensures consistent formatting and logging levels across the application.src/utils/logger.js (3)
1-17: Thorough documentation.The header doc block clearly explains the module’s purpose, usage, and environment configurations. This level of detail is beneficial for maintainers.
42-93: Sensible approach for info, warn, and error logs.Using different console methods (
console.log,console.warn,console.error) helps route output correctly. This separation, combined with label prepping, is an elegant design for a lightweight logger.
95-96: Export naming consistency is clear.Exporting all log functions under their straightforward names is intuitive for downstream usage.
src/index.js (6)
8-8: Aligned logger import.Importing
loggerearly on ensures consistent logging can be used throughout the file.
27-29: Expanded partials coverage.Including
Partials.ThreadMemberandPartials.Threadensures your bot can handle thread events. No issues here.
46-46: Server listening message.Registering a clear info log for the HTTP server is good practice to confirm the bot’s external interface is up.
68-68: Warning for incomplete command definitions.Consistent with your approach in
deploy_commands.js, this provides a straightforward notice to developers.
92-92: Globally set Discord client notification.Logging an info message once the client is ready, plus storing it in a global variable, is a clean and straightforward approach.
94-94: Error-handling consistency.Catching the login failure with
logger.errorkeeps error logs centralized. Great adherence to the new logging strategy.src/events/threadCreate.js (4)
1-4: Clear module documentation.The top-level doc block properly sets expectations about how new threads in specified forum channels will be converted into tickets.
19-20: Early exit for non-monitored channels.Efficiently ignoring threads not in
FORUM_CHANNEL_IDShelps reduce overhead and complexity.
48-77: Successful ticket creation flow.Creating and binding the ticket before notifying the thread provides a robust user experience. Good use of an embed to present ticket details.
78-96: Error-handling block.Thorough handling of timeouts vs. general errors. Attempting to notify users in the thread about errors is especially user-friendly.
src/events/interactionCreate.js (2)
3-4: Imports look good.The addition of
getKey,setKey, andloggeraligns with the rest of the application’s memory and logging strategy. No issues spotted here.
6-11: Good use of documentation.Providing a clear header comment block for the event handler helps with readability and maintainability.
src/services/unthread.js (1)
12-12: Logger import is appropriate.Replacing console logs with a structured logger enhances debugging consistency.
warengonzaga
added
the
maintainers only
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (5)
README.md (3)
17-23: Easy Deployment Section Introduced
The “Easy Deployment” section with Railway deployment instructions and a deploy button is a useful addition. It simplifies the setup process for users and provides a direct call to action.
139-141: Fenced Code Block Language Hint
Consider specifying a language (e.g.env) in the fenced code block demonstrating theFORUM_CHANNEL_IDSconfiguration to adhere to markdownlint recommendations.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
139-139: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
201-202: Credits and Attribution Update
The closing credit line now recognizes contributions by Waren Gonzaga, WG Technology Labs, and includes a quirky reference (“[Him]”). Please verify that the informal attribution aligns with the project’s tone and the team’s guidelines.LICENSE (2)
16-17: Terminology Consistency Check
The paragraph still uses the generic term “General Public Licenses.” Consider revising it to explicitly state “GNU Affero General Public Licenses” for consistent branding throughout the document.
27-28: Clarify Developer Rights Statement
The section starting with “Developers that use our General Public Licenses...” should be reviewed for consistent AGPL terminology. Aligning the language with the AGPL throughout can prevent potential confusion.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
LICENSE(5 hunks)README.md(4 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
README.md
139-139: Fenced code blocks should have a language specified
null
(MD040, fenced-code-language)
🪛 LanguageTool
README.md
[style] ~183-~183: Using many exclamation marks might seem excessive (in this case: 14 exclamation marks for a text that’s 8557 characters long)
Context: ...tars.github.com/nominate) as GitHub Star! 💫 ## 📋 Code of Conduct We're commit...
(EN_EXCESSIVE_EXCLAMATION)
🔇 Additional comments (14)
README.md (7)
3-3: Project Badges Added
The new badges clearly showcase key project information (release, sponsors, license, and stars) and promote the brand.
7-7: Updated Bot Description
The revised description now emphasizes the integration with Unthread and the streamlined support ticket creation. This enhances clarity for new users about the bot’s purpose.
12-12: Automatic Ticket Creation Feature Highlighted
The key feature list now includes automatic ticket creation from forum channel posts. This clearly informs users of the newly added functionality.
31-39: Enhanced Support Ticket Creation Instructions
The updated instructions for the/supportcommand now specify that the email field is optional, which aligns with the feature change. Clear, step-by-step directions improve user guidance.
40-44: Forum Channels Workflow Explained
The “Using Forum Channels” instructions detail the process of converting a forum post to a support ticket. This addition effectively supports the automatic ticket creation feature.
134-145: Configure Forum Channels Section Added
The new “Configure Forum Channels” section instructs users on adding forum channel IDs to the.envfile. This is crucial for enabling automatic ticket creation from forum posts.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
139-139: Fenced code blocks should have a language specified
null(MD040, fenced-code-language)
173-182: Updated Support Section with Multiple Options
The “🙏 Support” section now offers several ways to support the project (sponsorship, coffee, Railway deployment). This is a nice community-driven touch that encourages contributions.LICENSE (7)
1-2: License Header Update to AGPL
The header now correctly identifies the license as the GNU AFFERO GENERAL PUBLIC LICENSE Version 3 (dated 19 November 2007), reflecting the intended change from GPL to AGPL.
10-12: AGPL Preamble Clarification
The updated preamble clearly explains that the AGPL is designed with network server software in mind, ensuring community cooperation. This enhances the license’s intent for remotely accessed software.
563-566: Revised License Version Information
The section addressing revised versions of the license now correctly references the GNU Affero General Public License. This ensures that any future updates follow the intended AGPL structure.
569-574: License Version Choice Section Updated
The clause regarding choice of license versions now properly refers to the GNU Affero General Public License. This is clear and correct—well done.
633-638: Updated Copyright and License Terms
The copyright notice now reflects the current year (2025) and the license text has been updated to reference the GNU Affero General Public License. This section is accurately updated.
650-657: Remote Interaction Source Availability Clause
The instructions on providing access to the Corresponding Source for remote interactions are detailed and align with AGPL requirements. This is important for ensuring compliance.
660-661: Helpful Reference to AGPL Documentation
The final note provides a direct link to the official GNU AGPL documentation, which is valuable for users who need further clarification.
There was a problem hiding this comment.
Copilot reviewed 13 out of 16 changed files in this pull request and generated no comments.
Files not reviewed (3)
- .env.example: Language not supported
- LICENSE: Language not supported
- package.json: Language not supported
Comments suppressed due to low confidence (1)
src/services/unthread.js:142
- Consider adding unit tests to verify that the exponential backoff and jitter logic in the polling mechanism behaves as expected.
let delayMs = Math.min(
maxDelayMs,
baseDelayMs * Math.pow(2, attempt)
);
This pull request includes several changes to enhance the Unthread Discord Bot's functionality and improve logging. The most important changes include adding support for automatic ticket creation from forum posts, making the email input field optional, and replacing
consolestatements with a logger utility.Enhancements to functionality:
.env.exampleto includeFORUM_CHANNEL_IDSand added instructions inREADME.mdfor configuring forum channels. (.env.example[1]README.md[2] [3]ThreadCreateto convert new forum posts into support tickets and link them with Discord threads. (src/events/threadCreate.jssrc/events/threadCreate.jsR1-R95)Improvements to user interaction:
src/commands/support/support.js[1]src/events/interactionCreate.js[2]Logging improvements:
consolestatements with a logger utility across multiple files for consistent and structured logging. (src/deploy_commands.js[1] [2] [3];src/events/error.js[4];src/events/messageCreate.js[5] [6] [7] [8];src/events/ready.js[9] [10];src/index.js[11] [12]Miscellaneous:
src/index.jsto include additional gateway intents and partials for better handling of thread events. (src/index.jssrc/index.jsL20-R29)Summary by CodeRabbit
New Features
Documentation