Currently Implemented Search is Deprecated about linkedin HOT 6 CLOSED

I have a suspicion that this gem may need to be redone from the ground up to support a more flexible search model provided by people/search
The whole idea of field selectors doesn't fit into predefined set of profile attributes provided with this gem.
This is just an educated guess on my part

from linkedin.

Hi ckarbass and vladgurovich,

I am currently updating the gem to work correctly with the xml apis, this includes updating search which is out of date (pull requests are more than welcome as well).

Regarding redoing the gem from the ground up, this is currently going on in another branch (json api, hashie, multi_json, and maybe oauth2), but this will take a little longer than initially planned.

As for the field selectors, this is ingrained in the LinkedIn api, so there is not much I can do about it, but if you have some suggestions I am all ears.

I will leave this issue open until the search api is working as per the updated api.

Thanks,

Josh

from linkedin.

A simpler but slightly less readable approach would be to abandon individual objects such as languages, country, etc etc in favor of something like Hashie(or specifically Mash).
The problem of course is that due to dynamic nature of field selectors, the structure of returned data is not as strict as one provided by your current implementation and will probably require the end users of your gem to have some knowledge of linked in responses.
Oh, I just noticed the mashie branch :)

from linkedin.

Hey vladgurovich,

Once V0.2.0 of the gem is released all my efforts will be focused on the new Hashie (Mash) Json branch, 90% less code with 50% more functionality*.

Watch this space

Josh

*numbers are not quantifiable, but you get the picture :)

from linkedin.

Hi, there is a new a pull request for the new search api

from linkedin.

Works for me, feel free to reopen this.

from linkedin.