Skip to content
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

StreamResponse does not include the Next property #53

Open
emendezrivas opened this issue Mar 11, 2021 · 1 comment
Open

StreamResponse does not include the Next property #53

emendezrivas opened this issue Mar 11, 2021 · 1 comment

Comments

@emendezrivas
Copy link

emendezrivas commented Mar 11, 2021

The REST API includes the "next" property on the JSON, which indicates that another page of activities is available for fetching:

{ results: [], next: '/api/v1.0/feed/<< feed_group >>/<< feed_id >>/?api_key=<< api_key >>&id_lt=<< next_activity_id >>&limit=<< activity_limit >>' }

This is not being exposed on the StreamResponse object. It would be very helpful to have this property, as it could allow having an indicator that there is at least one more page available, since there is not a way to get the total count of activities on a feed for a specific user.

gz#10110

@shodgetts
Copy link

Agent comment from Stephen Hodgetts in Zendesk ticket #10110:

Hello, thanks for reporting this, we've got an engineer looking into it soon.

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

No branches or pull requests

2 participants