refactor!: adjusting max_af to max_carriers for inhouse

[holtgrewe]

Release-As: 0.16.0

Summary by CodeRabbit

• New Features

  • Introduced a new InhouseFrequencySettings option for enhanced filtration settings in queries.

• Bug Fixes

  • Updated QuerySettingsFrequency to correctly reference the new InhouseFrequencySettings.

• Tests

  • Enhanced test cases to validate the integration and functionality of the new in-house frequency settings.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve modifications to the query.proto file and the corresponding Rust implementation in query.rs. A new message, InhouseFrequencySettings, has been introduced to define in-house frequency settings, replacing the previous NuclearFrequencySettings in the QuerySettingsFrequency message. Additionally, comments in the proto file have been updated for clarity. The Rust struct has been updated to match these changes, and test cases have been adjusted to ensure functionality aligns with the new definitions.

Changes

File Path	Change Summary
protos/varfish/v1/seqvars/query.proto	- Added new message: InhouseFrequencySettings. - Updated QuerySettingsFrequency to use InhouseFrequencySettings instead of NuclearFrequencySettings. - Comments modified for clarity.
src/seqvars/query/schema/query.rs	- Added new struct: InhouseFrequencySettings. - Updated QuerySettingsFrequency to use InhouseFrequencySettings. - Modified conversion logic for InhouseFrequencySettings. - Updated test cases for compatibility with new structures.

Poem

🐇 In the meadow where changes bloom,
New settings sprout, dispelling gloom.
Inhouse filters now take flight,
With maximum counts shining bright.
A hop, a skip, a proto cheer,
Clarity reigns, the path is clear! 🌼

---

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71%. Comparing base (06ebb8a) to head (c54f463).
Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #512   +/-   ##
=====================================
  Coverage     71%     71%           
=====================================
  Files         43      43           
  Lines      11831   11841   +10     
=====================================
+ Hits        8501    8511   +10     
  Misses      3330    3330           

Files with missing lines	Coverage Δ
src/seqvars/query/schema/query.rs	97% <100%> (+<1%)	⬆️