Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Search to Listen.V1.WebSocket.Channel model #324

Merged

Conversation

ElliotEserin
Copy link

@ElliotEserin ElliotEserin commented Aug 5, 2024

Proposed changes

Issue - Add the Search property to the Listen WebSocket channel. This mirrors the current REST equivalent for the channel record. This property is deserialized from the JSON response returned by the Deepgram Response Schema

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

I thought I would give this a go myself and this is actually my first PR ever... So feel free to tell me how I could improve, or feel free to throw it out if it isn't good enough! I couldn't find anything in the contribution guidelines on this repos standards for linting, however the code is 100% copy-pasted from other areas of the project so hopefully it is suitable!

Summary by CodeRabbit

  • New Features
    • Introduced a new Search property in the audio Channel record for enhanced data handling.
    • Added a Hit record to encapsulate audio recognition details such as confidence level and timing.
    • Created a Search record to facilitate search queries, containing properties for query and results.

These additions improve the API's ability to manage and analyze audio recognition data effectively.

Copy link
Contributor

coderabbitai bot commented Aug 5, 2024

Walkthrough

The changes introduce new functionalities to the Deepgram .NET SDK by adding support for search queries in the Listen V1 WebSocket channels. This enhancement includes the addition of new data structures for handling search data, aligning the SDK's capabilities with the Deepgram API's existing features. The updates facilitate more efficient audio recognition and analysis by incorporating search results directly into the channel's data model.

Changes

File Change Summary
Deepgram/Models/Listen/v1/WebSocket/Channel.cs - Added public IReadOnlyList<Search>? Search { get; set; } property for search-related information.
Deepgram/Models/Listen/v1/WebSocket/Hit.cs - Introduced Hit record with properties: Confidence, End, Snippet, Start, and an overridden ToString method.
Deepgram/Models/Listen/v1/WebSocket/Search.cs - Created Search record with properties: Query (string) and Hits (IReadOnlyList), and an overridden ToString method.

Possibly related issues


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
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 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

@davidvonthenen
Copy link
Contributor

Awesome @ElliotEserin Thanks for opening up this PR!

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 24fb0e3 and 4689fce.

Files selected for processing (3)
  • Deepgram/Models/Listen/v1/WebSocket/Channel.cs (1 hunks)
  • Deepgram/Models/Listen/v1/WebSocket/Hit.cs (1 hunks)
  • Deepgram/Models/Listen/v1/WebSocket/Search.cs (1 hunks)
Additional comments not posted (9)
Deepgram/Models/Listen/v1/WebSocket/Channel.cs (1)

16-21: LGTM! The new property Search is well-defined.

The new property Search is correctly annotated and follows the existing patterns in the file.

Deepgram/Models/Listen/v1/WebSocket/Search.cs (3)

12-14: LGTM! The property Query is well-defined.

The property Query is correctly annotated and follows the existing patterns in the file.


19-21: LGTM! The property Hits is well-defined.

The property Hits is correctly annotated and follows the existing patterns in the file.


7-30: LGTM! The overall structure of Search record is well-defined.

The Search record is correctly structured and follows existing patterns in the project.

Deepgram/Models/Listen/v1/WebSocket/Hit.cs (5)

12-14: LGTM! The property Confidence is well-defined.

The property Confidence is correctly annotated and follows the existing patterns in the file.


20-22: LGTM! The property End is well-defined.

The property End is correctly annotated and follows the existing patterns in the file.


27-29: LGTM! The property Snippet is well-defined.

The property Snippet is correctly annotated and follows the existing patterns in the file.


34-36: LGTM! The property Start is well-defined.

The property Start is correctly annotated and follows the existing patterns in the file.


7-45: LGTM! The overall structure of Hit record is well-defined.

The Hit record is correctly structured and follows existing patterns in the project.

@ElliotEserin
Copy link
Author

No problem, I hope it's useful!

@davidvonthenen davidvonthenen merged commit 15d6783 into deepgram:main Aug 5, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants