people search should allow calling code to specify field list

[jbarefoot]

First, thank you Craig, Robert, and other contributors, for this wonderful API binding. This is not a bug, rather an enhancement request.

My issue begins with graph distance (1st, 2nd,3rd order connection), specifically I want to know what it is for a people-search call. This would seem like a fairly common use case, esp. since LinkedIn always displays that info in its own UI. Unfortunately the distance field is not one of the fields requested in this API's implementation of search, and I saw no way to add to the field list.

Obviously I could use the underlying RestOperations to make whatever calls I want and specify the return fields I want. That's not particularly satisfying though, because I would like to use the already-configured ObjectMapper to map the result. Can't do it though, as it is private with no accessor. I started hacking together an extension to do what I want, but it was frankly very unsatisfying due to a lot of private and package-level visibility throughout the project, so I've begun modifying the source for RC1 and included it in my own project instead.

Also in general there is a mis-match between the mapping classes (LinkedInProfile and LinkedInProfileFull) and the r_basicprofile and r_fullprofile permissions. In particular, location, distance, and num-connections are part of r_basicprofile and available as part of the /connections API call, but missing from LinkedInProfile:
https://developer.linkedin.com/documents/profile-fields#profile

I understand that changing this would mean that some fields in LinkedInProfile may be null depending on the fields requested. Frankly I don't see that as an issue, because it already happens all the time for LinkedInProfileFull depending on what LinkedIn member you query.

Long-winded way of saying...I humbly request that:
1)The profile mapping classes match the possible fields according to LinkedIn permissions and what's available for different API calls.
2) It be possible for calling code to specify the set of fields requested, ideally for any call but especially for people-search.

If the contributors agree with the above, I can attempt to make my changes in a generically useful fashion and afterwards I can create a patch from RC1 and apply it to a fork of the current github master, create a pull request, yada-yada.

Otherwise I'll hack away, and leave you guys in peace. :)