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
Describe the bug When using a plain output, dasel converts the values and does not display them as plain, which also affects the selection of values.
For instance, integer values are being converted to exponent notation.
To Reproduce
$ echo '[4090849286]' | dasel -r json -w - '.all()' 4.090849286e+09 $ echo '[4090849286]' | dasel -r json '.all()' 4090849286 $ echo '{"foo": "bar"}' | dasel -r json ".filter(equal(foo,bar))" { "foo": "bar" } $ echo '{"foo": 12345678}' | dasel -r json ".filter(equal(foo,12345678))" $ echo '{"foo": 12345678}' | dasel -r json ".filter(equal(foo,1.2345678e+07))" { "foo": 12345678 }
Expected behavior
dasel should not convert the values to any type and keep them as is so plain output and selection/filtration will work as expected.
Desktop (please complete the following information):
Relates to #245, #293
The text was updated successfully, but these errors were encountered:
cc @TomWright
Sorry, something went wrong.
This issue is caused by the fact that all comparisons are string comparisons.
The best way to solve this is to allow functions to accept arguments of different types.
The given example causes a comparison on the following types, which is obviously false since they are strings.
12345678.000000 string, 12345678 string
This has been fixed here: 7e2937e
It's not merged to master or released yet but will be included in the larger set of encoding/decoding changes
FYI This has been merged to master and is available in the development version. This will be included in the next relase.
No branches or pull requests
Describe the bug
When using a plain output, dasel converts the values and does not display them as plain, which also affects the selection of values.
For instance, integer values are being converted to exponent notation.
To Reproduce
Expected behavior
dasel should not convert the values to any type and keep them as is so plain output and selection/filtration will work as expected.
Desktop (please complete the following information):
Relates to #245, #293
The text was updated successfully, but these errors were encountered: