Seems to choke on boolean argument values
See original GitHub issueDescribe the bug While parsing a query with a boolean argument it fails and I see:
Error: Parse error: Failed to parse operation "WHATEVER" => varName.indexOf is not a function
To Reproduce Steps to reproduce the behavior:
- Create a query with a boolean argument
- Try to parse it
- Feel sad
Expected behavior I expected to see my query succeed.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: macOS
- Browser: Firefox
- Version: Latest
Additional context This is a great module, thanks for creating it.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
What is wrong with boolean parameters?
A boolean argument indicates the function has 2 different behaviors. These 2 behaviors are probably tangled together. And this just calls for more....
Read more >while (Boolean condition) statement;
A compound statement is a bunch of statements enclosed by curly braces! } • A Boolean condition is either true or false. •...
Read more >Lua error did not pass boolean - Stack Overflow
The and operator returns its first argument if that value is something considered non-true, and its second argument otherwise.
Read more >Issue with Boolean types in code generated by swagger ...
Here in the spec, it seems that Booleans can be true or false , without quotes. This is matched in the Ansible documentation...
Read more >Clean code: The curse of a boolean parameter | by Alex Curran
Whilst there are simply two values of a boolean, true or false *, the fact they introduce a branch into your code is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah! I’ll try to look up to your solution and update the code here! Thanks!
The problem with #33 is not actually the
null
value, it’s some sort of parsing problem in the parser itself, but it crashes before thenull
. Probably because it is identifying the object as a variable