Add a service to allow equivalent of search/wsuser

[rfay]

The Android app is using search/wsuser directly because it provides a simple search capability (full name, town, email) all in one string. However, the app is currently scraping to use it, which makes it fragile. (See warmshowers/wsandroid#69)

It should be easy to refactor and move the search/wsuser (hook_search) stuff into a place where it can be wrapped by a RESTful service, making this more robust.

wsuser_search is an invocation of hook_search(). The thing we have to do is wrap the query part so it's usable by both the service and hook_search.

[klzig]

I'll add search to the windows app if you add it to the REST service.

[tmelz]

Any plans to implement this soon?

[rfay]

No immediate plans PRs are welcome.

[rfay]

Working on this soon. The biggest problem with the android app (warmshowers/wsandroid#73) really just cascades from the lack of this.

[klzig]

Good timing for the WP app, I'm about to begin working on an update.

[rfay]

Added hosts by_keyword in e3943ea

[rfay]

This is deployed live, and is described in https://github.com/warmshowers/Warmshowers.org/wiki/Warmshowers-RESTful-Services-for-Mobile-Apps#bykeyword

[klzig]

Thanks Randy! Will this return users who are currently unavailable?

[rfay]

Yes, just like the warmshowers.org/search/wsuser, it can be used to search for any user. The currently available member of the array though lets you know what the status is.