You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Briefly, train_discrete() and train_continuous() throw errors that can be hard to debug in some cases.
If tidyverse/ggplot2#5086 is merged, that would leave responsibility over Range classes with {scales}, so that is why I'm opening this issue here.
My proposal would be that the Range classes get an optional field with a scale name or aesthetic name that can be used for communicating more informative errors. Responsibility for providing an informative field would then bounce the ball back to ggplot2.
The text was updated successfully, but these errors were encountered:
This suggestion is lifted over from tidyverse/ggplot2#4258.
Briefly,
train_discrete()
andtrain_continuous()
throw errors that can be hard to debug in some cases.If tidyverse/ggplot2#5086 is merged, that would leave responsibility over Range classes with {scales}, so that is why I'm opening this issue here.
My proposal would be that the Range classes get an optional field with a scale name or aesthetic name that can be used for communicating more informative errors. Responsibility for providing an informative field would then bounce the ball back to ggplot2.
The text was updated successfully, but these errors were encountered: