-
Notifications
You must be signed in to change notification settings - Fork 40
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
refactor: Exchange of the canonical function #336
Conversation
WalkthroughThe changes involve updates to the YAML configuration for variant calls, specifically altering the Changes
Possibly related PRs
Suggested reviewers
Poem
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? 🪧 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 (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
workflow/resources/datavzrd/variant-calls-template.datavzrd.yaml
(2 hunks)
🔇 Additional comments (2)
workflow/resources/datavzrd/variant-calls-template.datavzrd.yaml (2)
307-312
: LGTM: Boolean visualization configuration looks good!
The spell configuration for boolean values is properly structured with appropriate true/false value mappings.
307-312
: Verify documentation for the visualization change
The switch from heatmap to boolean spell visualization is a significant change that might affect users. Please ensure that:
- The documentation is updated to reflect this change
- A migration guide is provided if needed
- The change is mentioned in the changelog
Also applies to: 482-487
spell: | ||
url: v1.1.3/logic/boolean | ||
with: | ||
true_values: "true" | ||
false_values: "false" | ||
custom-content: ?empty_content |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix inconsistent configuration keys between coding and non-coding sections
The boolean spell configuration uses different key names in the coding and non-coding sections:
- Coding section:
true_value
,false_value
- Non-coding section:
true_values
,false_values
(plural)
This inconsistency could cause the non-coding section to fail. Both sections should use the same key names.
Apply this fix to maintain consistency:
spell:
url: v1.1.3/logic/boolean
with:
- true_values: "true"
- false_values: "false"
+ true_value: "true"
+ false_value: "false"
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
spell: | |
url: v1.1.3/logic/boolean | |
with: | |
true_values: "true" | |
false_values: "false" | |
custom-content: ?empty_content | |
spell: | |
url: v1.1.3/logic/boolean | |
with: | |
true_value: "true" | |
false_value: "false" | |
custom-content: ?empty_content |
Boolean spell is used instead of a heatmap.
Summary by CodeRabbit
hgvsp
andhgvsc
columns to enhance data visualization with a new boolean logic representation.