-
Notifications
You must be signed in to change notification settings - Fork 31
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
Ordered treated as numbers #63
Comments
Allowing textual thresholds seems to break a lot of assumptions. Initial work in separate |
Previous commit is a workaround to convert through a character vector if possible (keeping numeric values if the ordered values are numbers). There is now a warning in case of a conversion to integer values. |
The 1.16 release will have the previous workaround to use the correct numbers (if actually numbers) or warn the user. Once we return a data.frame by default, and |
Only makes sense if ordered values are actually 1, 2, ... n
Steps to reproduce:
The text was updated successfully, but these errors were encountered: