Skip to content

allow values to be supplied to new_quant_param() on its own without range and inclusive #228

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

Merged
merged 1 commit into from
Apr 21, 2022

Conversation

hfrick
Copy link
Member

@hfrick hfrick commented Apr 21, 2022

closes #87

without `range` and `inclusive`
@hfrick hfrick merged commit 79dff12 into main Apr 21, 2022
@hfrick hfrick deleted the fix/values-alone branch April 21, 2022 18:22
@github-actions
Copy link

github-actions bot commented May 6, 2022

This pull request 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.

@github-actions github-actions bot locked and limited conversation to collaborators May 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

new_quant_param with discrete values shouldn't require range
1 participant