On Jul 29, 2014, at 4:14 PM, Jens Alfke <jens....@gmail.com> wrote:I just took a minute to debug this. The answer is simply that there isn't any support (yet) for JavaScript-based filters. The JavaScriptCore integration only supports views (map and reduce functions) so far.
Ah, most excellent!Yes, the invalid JSON is just my sloppiness.Eagerly awaiting Chris to rebuild the phone gap plugin.How do I know when this gets done?
Eagerly awaiting Chris to rebuild the phone gap plugin.How do I know when this gets done?On my plate for this week is to cut a 1.0.1 release of PhoneGap (I don't think this will have your fixes, but as soon as I have 1.0.1 done I'll start work on 1.1) 1.1 will include the filter stuff. It will also drop support for iOS 6. (Although we could maintain a parallel version that supports iOS 6 if there is strong demand.)So my guess is that we'll have something you can play with early next week. Here's the bug to follow / ping me on if it takes longer than a week.
On Wednesday, July 30, 2014 6:40:31 PM UTC-7, J. Chris Anderson wrote:Eagerly awaiting Chris to rebuild the phone gap plugin.How do I know when this gets done?
Thanks Chris.I'm testing it out. I'm using the main GIT repository URL I've been using since it seems to be up-to-date. If that assumption is incorrect, please let me know.What I'm seeing is that I no longer get a 404. But I'm not getting any change notifications, either.
Yeah, I just tried a filter that returns true no matter what, and still doesn't work.I get a change notify from the http socket that does not utilizes the filter, but none from the one that does.
throw JSON.stringify(req);
}
will make them show up in the Xcode logs. In the case of the first code I tested, anything but numbers and true or "false" would fail to parse as a parameter. Now it works great, but you may have to decodeURIComponent and JSON.parse parameters in your filter function (or switch to a comma separated list or something easier to decode.)
Chris