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
Based on the tests, it seems that it's intentional for dynamic typing to treat true, false, and TRUE, FALSE as booleans, leaving True and False as strings: https://github.com/mholt/PapaParse/blob/master/tests/test-cases.js#L921-L924
true
false
TRUE
FALSE
True
False
Curious what is the rationale behind the decision?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Based on the tests, it seems that it's intentional for dynamic typing to treat
true
,false
, andTRUE
,FALSE
as booleans, leavingTrue
andFalse
as strings: https://github.com/mholt/PapaParse/blob/master/tests/test-cases.js#L921-L924Curious what is the rationale behind the decision?
The text was updated successfully, but these errors were encountered: