Skip to content
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

TRUE/FALSE should be booleans not strings #16

Open
quantizor opened this issue Nov 30, 2013 · 1 comment
Open

TRUE/FALSE should be booleans not strings #16

quantizor opened this issue Nov 30, 2013 · 1 comment

Comments

@quantizor
Copy link

Hi! First, awesome tool. Love it.

A big improvement (IMO) would be native conversion of TRUE and FALSE (case-insensitive) to the lowercase, unquoted true/false JSON equivalents. Currently, they are outputted as strings, which is somewhat counterintuitive since numbers are outputted as numbers and not stringified ones.

@dosstx
Copy link

dosstx commented Jan 21, 2015

I agree this is much needed. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants