revert: keyterm -> keyterms

[naomi-lgbt]

Proposed changes

Types of changes

What types of changes does your code introduce to the community .NET SDK?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update or tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have lint'ed all of my code using repo standards
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

Summary by CodeRabbit

• Refactor

  • Key term configuration has been updated to support multiple entries for greater flexibility and consistency.

• Documentation

  • Updated guidance now clarifies key term usage, with additional reference details to assist with setup.

[coderabbitai]

Walkthrough

The pull request renames a property from singular to plural across multiple components. In the Client class, the conditional check is updated to inspect the plural property. In the Listen record, the property is renamed from Keyterm to Keyterms, the JSON attribute is updated accordingly, and XML documentation is added. The sample configuration in the example program is similarly updated to use the plural property name.

Changes

File(s)	Change Summary
Deepgram/.../Websocket/Client.cs	Updated the conditional check in the Connect method to verify options.Agent.Listen.Keyterms?.Count > 0 instead of Keyterm?.Count > 0.
Deepgram/.../Listen.cs	Renamed the property from Keyterm to Keyterms, updated the JSON property name from "keyterm" to "keyterms", and added XML documentation.
examples/.../Program.cs	Modified the configuration assignment to use Keyterms instead of Keyterm.

Possibly related PRs

• feat: support nova 3 and keyterms #363: This PR makes related changes by addressing key term handling, aligning the updates in property naming and usage within the client and model classes.

Suggested reviewers

• jpvajda

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 138ce74 and 4996358.

📒 Files selected for processing (3)

• Deepgram/Clients/Agent/v2/Websocket/Client.cs (1 hunks)
• Deepgram/Models/Agent/v2/WebSocket/Listen.cs (1 hunks)
• examples/agent/websocket/simple/Program.cs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build

🔇 Additional comments (4)

examples/agent/websocket/simple/Program.cs (1)

199-199: Property name updated to match semantic meaning.

The property name has been changed from Keyterm to Keyterms to better reflect that it's a collection of multiple key terms.

Deepgram/Clients/Agent/v2/Websocket/Client.cs (1)

55-55: Updated property reference to match renamed property.

The condition has been updated to check options.Agent.Listen.Keyterms?.Count > 0 instead of the previous Keyterm property, maintaining consistency with the property rename in the Listen class.

Deepgram/Models/Agent/v2/WebSocket/Listen.cs (2)

13-16: Added XML documentation for the Keyterms property.

Good addition of XML documentation that explains the purpose and benefits of Keyterm Prompting, including the link to further documentation.

---

18-19: Property and JSON attribute renamed from singular to plural form.

The property has been renamed from Keyterm to Keyterms along with its corresponding JSON property name, making it consistent with its purpose as a collection of key terms.

✨ 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.