Sorry for not getting back to the other issue we discussed some weeks ago: I had to shave a few yacks and here I am making a PR for querying a new v2 users endpoint :)
This is a first draft just to start the discussion:
is this approach fine?
Is there any particular way you wish to see pagination implemented?
Possibly:
provide a kind of stream?
A Future of a possibly very long list?
Leaving pagination to the API user?
something else?
Definitely not urgent.
Comments on naming/structure welcome as well. Basically this:
adds a new case class for deserializing paginated results (alternative would be to merge it to the existing result type and make the metadata optional?)
adds a new TwitterUserFollowsClient trait
Kindly,
Julien
PS: will look into tests once we agree on the structure :)
Hello @DanielaSfregola,
Sorry for not getting back to the other issue we discussed some weeks ago: I had to shave a few yacks and here I am making a PR for querying a new v2 users endpoint :)
This is a first draft just to start the discussion:
Possibly:
provide a kind of stream?
A Future of a possibly very long list?
Leaving pagination to the API user?
something else?
Definitely not urgent.
Comments on naming/structure welcome as well. Basically this:
adds a new case class for deserializing paginated results (alternative would be to merge it to the existing result type and make the metadata optional?)
adds a new
TwitterUserFollowsClienttraitKindly, Julien
PS: will look into tests once we agree on the structure :)