-
Notifications
You must be signed in to change notification settings - Fork 45
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
Values from variant file are always evaluated as a string and not boolean #691
Comments
Side note: in |
what should be allowed? Strings and bools? It's not yet specified properly, I guess. I don't think we want floats. I am not sure about integers. conda-build has some wicked magic to turn floats into version strings, but I also think we don't want that (it's lossy and not accurate, too). |
I think strings and bools ( |
A couple of months ago I created #232. Should we just let the user decide of the type they want? Floats are more special since YAML doesn't like to have |
For a float So I would argue that we should either only allow strings or allow strings and bools and either nothing else or integers. |
I would be in favor of strings and bools. But shouldn't this kind of decision be done in a CEP? |
if: new_pydantic == 'true'
fixes the issue.if: new_pydantic
still evaluates to true even if the value isfalse
.IMO rattler-build should either throw an error here since
new_pydantic
is only a string and implicit casting to bool can cause issues (like in this example) or properly cast it to boolean.Please also add tests for this behavior 🙏🏻
The text was updated successfully, but these errors were encountered: