-
Notifications
You must be signed in to change notification settings - Fork 80
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
Warnings about aesthetic length and no non-missing argument to min in visualise + shade_p_value functions #528
Comments
Thank you, I can reproduce! Both CRAN and dev infer see these warnings. Some notes-to-self... With the previous ggplot2 release, 3.4.4, one is addressed but the other is still there: # pak::pak("tidyverse/ggplot2@v3.4.4")
library(dplyr)
#>
#> Attaching package: 'dplyr'
#> The following objects are masked from 'package:stats':
#>
#> filter, lag
#> The following objects are masked from 'package:base':
#>
#> intersect, setdiff, setequal, union
library(forcats)
library(infer)
set.seed(123)
gss <- gss |>
mutate(class = fct_drop(class))
h0 <- gss |>
specify(class ~ college) |>
hypothesise("independence") |>
generate(1000, "permute") |>
calculate("chisq")
hA <- gss |>
specify(class ~ college) |>
calculate("chisq")
# two warnings
visualise(h0) +
shade_p_value(hA, "right")
#> Warning in min(diff(unique_loc)): no non-missing arguments to min; returning
#> Inf Created on 2024-03-25 with reprex v2.1.0 Same output with with 3.4.0, only warnings with 3.3.0 are |
The warnings come from |
Lines 182 to 187 in 7c7c3aa
Related to tidyverse/ggplot2#5762. |
Thanks for your prompt follow-up @simonpcouch. Very happy that this bug is fixed! |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
The problem
When running the visualise + shade_p_value function on a generated and or calculated dataset I receive two warnings:
Could the cause of these warnings be in the recent ggplot2 release?
Thanks in advance for looking into the issue.
Regards,
Pieter Vreeburg
Reproducible example
Created on 2024-03-25 with reprex v2.1.0
Session info
The text was updated successfully, but these errors were encountered: