We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi!
With #27 and its release in v0.9.5 a bug was introduced: nil values are converted to 0, 0.0 or '' if allow_nil is not allowed.
nil
0
0.0
''
allow_nil
I think that the behavior should be that a nil should be allowed if option is enabled, but if not, the value should remain.
So, in the Integer case, I would suggest:
Integer
case value when nil then options[:allow_nil] ? nil : value ...
The text was updated successfully, but these errors were encountered:
hey, sorry for the long delay. Thanks for the report!
I think it will be a good idea to fix it. Do you want to prepare PR?
Sorry, something went wrong.
No branches or pull requests
Hi!
With #27 and its release in v0.9.5 a bug was introduced:
nil
values are converted to0
,0.0
or''
ifallow_nil
is not allowed.I think that the behavior should be that a nil should be allowed if option is enabled, but if not, the value should remain.
So, in the
Integer
case, I would suggest:The text was updated successfully, but these errors were encountered: