-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Java client to Search API v3 [$50] #29
Comments
If you are considering solving this issue, you might be interested in also solving one or more of the following issues (they also have bounties from https://www.bountysource.com/) |
@xSAVIKx interested in the bounty here? :) |
@dentarg Yea, why not? :-) |
@dentarg should we support both v.2 and v.3 API? Update: Also, I'd need some API key to test changes, could you please send me one? |
Hi,
Correct, no need to keep v.2 support.
Oh, we should have documented it, but you can register for a free trial (full API access) at https://app.twingly.com/signup |
I've submitted a PR with updates to the v3 API. I'd also ask to increase the bounty if it is possible, cause I've also closed #28 with my updates in order to support compression. Regards, |
Update the client to use the new Blog Search API v3.
Notable changes from the previous version of the Blog Search API are listed under https://developer.twingly.com/resources/search#changes-from-previous-version.
The ruby client was updated in twingly/twingly-search-api-ruby#65, which can be used as help. Some XML fixtures can also be copied from there if needed.
If possible, try to keep all classes/methods/properties backwards compatible with the previous version of the client by marking methods as deprecated. Similar to what was done in the Ruby client.
Did you help close this issue? Go claim the $50 bounty on Bountysource.
The text was updated successfully, but these errors were encountered: