Skip to content
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.

StatusesFilterEndpoint Locations Issue #19

Closed
thaerlabs opened this issue Mar 3, 2013 · 4 comments
Closed

StatusesFilterEndpoint Locations Issue #19

thaerlabs opened this issue Mar 3, 2013 · 4 comments

Comments

@thaerlabs
Copy link

There is a problem using endpoint.locations(List)
Calling Joiner.on(',').join(locations) gives me

com.twitter.hbc.core.endpoint.Location@3794d372

and not what it should be 42.692871,16.972741,46.933594,29.152161

@xsl
Copy link
Contributor

xsl commented Mar 4, 2013

yep, submitted a pull request: #23

@thaerlabs
Copy link
Author

Can you please provide a snippet on how to use it?
It doesn't seem to work for me...

@xsl
Copy link
Contributor

xsl commented Mar 6, 2013

Are you still using the snapshot? The current stable version (1.3.0) still has this bug. You'll need to use the snapshot version for now

Here's a code snippet (you can replace StatusesSampleEndpoint in the runnable example code with this):

StatusesFilterEndpoint endpoint = new StatusesFilterEndpoint();
endpoint.locations(Lists.newArrayList(
  new Location(new Location.Coordinate(-122.75, 36.8), new Location.Coordinate(-121.75, 37.8))) // San Francisco
);

@kevinoliver
Copy link
Contributor

Should be fixed in 1.3.1 by #23

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants