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
When a file is passed as an argument, we should use the file extension as a input type hint unless an explicit --input parameter is passed.
--input
$ lq . .rustup/settings.toml "default_toolchain = \"stable-x86_64-unknown-linux-gnu\" profile = \"default\" version = \"12\"\n[overrides]"
Unwieldy long string, yaml parse of a single string representation of the whole document including newlines.
$ lq --input=toml . .rustup/settings.toml { "default_toolchain": "stable-x86_64-unknown-linux-gnu", "overrides": {}, "profile": "default", "version": "12" }
For at least these formats of filename, lq should just do the right thing.
lq
$ lq . doc.json
$ lq . doc.yaml
$ lq . doc.yml
$ lq . doc.toml
The text was updated successfully, but these errors were encountered:
Ah, that is a nice suggestion. Thank you. Would simplify usage a bit as well. I can have a quick go at this.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
When a file is passed as an argument, we should use the file extension as a input type hint unless an explicit
--input
parameter is passed.Current behavior
Yaml parse without argument
Unwieldy long string, yaml parse of a single string representation of the whole document including newlines.
Expected json output
Desired behavior
For at least these formats of filename,
lq
should just do the right thing.$ lq . doc.json
$ lq . doc.yaml
/$ lq . doc.yml
$ lq . doc.toml
The text was updated successfully, but these errors were encountered: