Tom Wright
Tom Wright
I am away on holiday for the next week. A PR is welcome, if not there will be a little wait
Could you raise a PR for this please? I don't use Windows so am unable to test
Hey @blurayne, my guess this is how the yaml parser is interpreting the value. Does it help if you change the original file to be `value: ""`?
Thanks for the info. I'll do some digging when I get a chance
This is only an issue when writing to CSV: ``` $ echo '[{"z":1,"a":2,"c":3},{"z":1,"a":2,"c":3}]' | dasel -r json [ { "z": 1, "a": 2, "c": 3 }, { "z": 1, "a":...
I dealt with this briefly yesterday and gave some quick workaround options here: https://github.com/TomWright/dasel/issues/390 I plan on adding clear instructions/workarounds for windows 7 users, and potentially adding a new build...
@sergeevabc it's not about hesitation... It's about the fact that I maintain this in my spare time and have an incredibly busy life at the moment. This is an open...
> (caveat: reflection isn't supported, so the default json package can't be used) This caveat causes quite the problem - A large majority of code in dasel uses reflection
@pmeier Heard and listened. In v3 (still in development) this is implemented as: ``` $ cat one.json { "foo": 1 } $ cat two.json { "bar": 2 } $ daselv3...
I've deleted the comment above because of safety concerns. It contained a phishing/malicious link.