Repository navigation
Dev #106
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
Dev #106
Changes from all commits
baad851
c9899cd
a08bb44
5a35d35
a72615b
60b139b
3467c91
3ba9d24
aecf5b7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Problem:
.resolveColToFill()returnsNAwhencolexceeds the length of a custompalette_use, so the plot can lose its fill or fail inside ggpubr. Trigger: This happens with calls such asqviolin(data, col = 3, palette_use = c("red", "blue")), even though the documentation accepts any positive palette index. Fix: Add the required compact input assertion and either reject out-of-range indexes or define how custom palettes should be extended.AGENTS.md reference: AGENTS.md:L13-L13
Useful? React with 👍 / 👎.