You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Going to fix this in greatcare/rql, so that null values no longer get coerced. This is probably due to the special-case treatment of null in the first lines of query's encodeValue.
The text was updated successfully, but these errors were encountered:
rkaw92
added a commit
to greatcare/rql
that referenced
this issue
Dec 21, 2016
This also includes a refactoring of the query module's `encodeValue` function for clarity and easier modification later, if necessary. Comments included.
For persvr#76
I'm uncertain about my status to contribute to open source. I believe it's probably ok for me to merge something like this (since I'm not the author) but since I'm not certain I'd rather not. I know I can get permission to contribute code I've authored by having my contributions reviewed and approved by my employer before contributing but that extra step is just enough of a burden to make it more effort than I have the time and energy for right now. I'm not sure who else could merge it.
Simple test case:
Expected output:
eq(foo,null)
Actual output:
eq(foo,string:null)
Going to fix this in
greatcare/rql
, so that null values no longer get coerced. This is probably due to the special-case treatment of null in the first lines of query'sencodeValue
.The text was updated successfully, but these errors were encountered: