revert: keyterm -> keyterms

[naomi-lgbt]

Summary by CodeRabbit

• New Features
  • Updated the listening configuration to support multiple key phrases for enhanced flexibility.
  • Streamlined the listening settings structure, simplifying customization and setup for improved user experience.

[coderabbitai]

Walkthrough

This update changes the agent's listening configuration by renaming the configuration key from a singular form (keyterm) to a plural form (keyterms). The sample file reflects this change, while the schema definition in the TypeScript file is refactored. The AgentLiveSchema now consolidates two union types into a single object shape with a model property and an optional keyterms array instead of a single string. No changes to the logic or control flow were made.

Changes

File(s)	Change Summary
examples/node-agent-live/index.js src/.../AgentLiveSchema.ts	Renamed the configuration property from keyterm to keyterms. In AgentLiveSchema.ts, the listen property was refactored from a union type with two object shapes to a single object shape featuring model: ListenModel and an optional keyterms array of strings.

Possibly related PRs

• fix: type definition issues on agent schema #358: Updates to the AgentLiveSchema interface structure, notably the introduction of the optional keyterms property, align with these changes.
• feat: add support for nova 3 and keyterms #359: The renaming of keyterm to keyterms in the listening configuration is directly related to modifications in this PR.
• fix: keyterms to keyterm #363: The shift from a singular to a plural key in the listening configuration reflects adjustments in the expected property structure similar to those in this PR.

Suggested reviewers

• jpvajda

✨ Finishing Touches

• 📝 Generate Docstrings

---

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 generate docstrings to generate docstrings for this 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/lib/types/AgentLiveSchema.ts (1)

157-166: Schema simplification looks good, but JSDoc link needs updating

The refactoring of the listen property from a union type to a single object structure with an optional keyterms array is a good simplification. However, the JSDoc comment on line 163 still references the singular form in the URL: "https://developers.deepgram.com/docs/keyterm".

Update the JSDoc URL to match the new plural property name:

/**
 * @see https://developers.deepgram.com/docs/keyterm
 */
keyterms?: string[];

to

/**
 * @see https://developers.deepgram.com/docs/keyterms
 */
keyterms?: string[];

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b39256d and de9c0a4.

📒 Files selected for processing (2)

• examples/node-agent-live/index.js (1 hunks)
• src/lib/types/AgentLiveSchema.ts (1 hunks)

🔇 Additional comments (1)

examples/node-agent-live/index.js (1)

31-31: LGTM: Configuration property updated to keyterms

The change from keyterm to keyterms correctly aligns with the schema update in AgentLiveSchema.ts. The array format is appropriate for the new property type.